commit | 14c9979047bb4ecd30619a9184e446c2e87fec26 | [log] [tgz] |
---|---|---|
author | karanmehta93 <k.mehta@salesforce.com> | Thu Oct 10 08:31:08 2019 -0700 |
committer | Enrico Olivelli <eolivelli@gmail.com> | Thu Oct 10 17:31:08 2019 +0200 |
tree | 42469c50b22100b6fa0d8a057aedfd02d686b89c | |
parent | 2f996dcf0159f945f7ec97ce7402e5d293009444 [diff] |
Add documentation for ByteBuffer lifecycle when adding entries Descriptions of the changes in this PR: Adding documentation for the issue [here](https://github.com/apache/bookkeeper/issues/2138) as discussed [here](https://github.com/apache/bookkeeper/issues/2138#issuecomment-522099668). Master Issue: #2138 Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2175 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.