commit | e3d807a32a0a9b69d0ac8db3ca17398373dbee28 | [log] [tgz] |
---|---|---|
author | Like <like_0903@163.com> | Fri Mar 29 12:45:33 2019 +0800 |
committer | Sijie Guo <guosijie@gmail.com> | Thu Mar 28 21:45:33 2019 -0700 |
tree | 70198f0c062a7c5384edc3786be56d06020e7614 | |
parent | 9524a9f4a82dd990aa437a2931bf2e5541ea0a37 [diff] |
Fix IDE complain as there are multi choices for error code There are two ```Code``` in ```org.apache.bookkeeper.client. BKException```: The first is https://github.com/apache/bookkeeper/blob/f26a4cae0e9205ad391c6d4d79f2937871864c28/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/BKException.java#L136 The second is https://github.com/apache/bookkeeper/blob/f26a4cae0e9205ad391c6d4d79f2937871864c28/bookkeeper-server/src/main/java/org/apache/bookkeeper/client/api/BKException.java#L180 BKException's subclasses cannot auto choice which ```Code```. Reviewers: Sijie Guo <sijie@apache.org> This closes #1999 from liketic/fix-code
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.