commit | 71f8e160b2e8cd16cb18bc186fcd67887150403e | [log] [tgz] |
---|---|---|
author | Tboy <guo.jiwei@immomo.com> | Thu Oct 29 10:15:59 2020 +0800 |
committer | GitHub <noreply@github.com> | Wed Oct 28 19:15:59 2020 -0700 |
tree | 68390b825851cd14f46a69450400d6542ead9b43 | |
parent | d8683b09d6452c08923941391a5926dca4080194 [diff] |
ISSUE #2454: Typo of naming LedgerStorage#setExplicitlac Fix #2454 . Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2456 from Technoboy-/issue-2454, closes #2454
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.