commit | 42e77802c025964d826c3b57e8f18c4bc464c481 | [log] [tgz] |
---|---|---|
author | Ivan Kelly <ivank@apache.org> | Sun Apr 28 04:06:24 2019 +0200 |
committer | Sijie Guo <guosijie@gmail.com> | Sun Apr 28 10:06:24 2019 +0800 |
tree | 80dd0bfeb7e5c1731a769aef16db3997cf49b872 | |
parent | 86bce12b58f997430f87771abb95854ee41a7248 [diff] |
DLog Namespace#openLog should declare LogNotFoundException Other methods such as delete do, so openLog should declare it to be consistent and to give users a hint that it can be caught. Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2072 from ivankelly/dl-openlog-ex
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.