commit | 14c445dae3976ec314ec7d1bac0e2d30a9d0e4c0 | [log] [tgz] |
---|---|---|
author | karanmehta93 <k.mehta@salesforce.com> | Thu Oct 24 14:39:01 2019 -0700 |
committer | Charan Reddy Guttapalem <reddycharan18@gmail.com> | Thu Oct 24 14:39:01 2019 -0700 |
tree | 86c707e396cbb89dab7a62d515795b84c874d020 | |
parent | 4872b1f2bbdb0cdde72ed7922b8de25dc17f58de [diff] |
Journal scan should throw IOException when it reads negative length Descriptions of the changes in this PR: ### Motivation During journal replay, we can encounter negative length value if there is journal corruption. Currently, due to this bug, we pass negative length to limit a buffer, which throws IllegalArgumentException. ### Changes Updated the Journal class to throw `IOException` with a clear message, instead of unclear `IllegalArgumentException`. Master Issue: #2176 Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Charan Reddy Guttapalem <reddycharan18@gmail.com> This closes #2177 from karanmehta93/master
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.