commit | 45871dccbb72a5aee30f7bbfaacfa0d6c2c202a5 | [log] [tgz] |
---|---|---|
author | liudezhi <33149602+liudezhi2098@users.noreply.github.com> | Mon Apr 13 15:26:07 2020 +0800 |
committer | GitHub <noreply@github.com> | Mon Apr 13 09:26:07 2020 +0200 |
tree | c6f1475a21c498727a4676e1926de47f2e09d8f0 | |
parent | e7430ce25e3609bf77b028e4f0475dad2147c22d [diff] |
Fix batch read data in cache does not take effect Descriptions of the changes in this PR: ### Motivation Fix batch read data in cache does not take effect ### Changes (Describe: what changes you have made) Master Issue: #2230 Fixes: #2230 Reviewers: Jia Zhai <zhaijia@apache.org>, Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None> This closes #2231 from liudezhi2098/issue-branch-xxx
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.