commit | 2a1cfe249830f8dee0570031c8d0c132c32fe24e | [log] [tgz] |
---|---|---|
author | vzhikserg <vzhikserg@users.noreply.github.com> | Sat Jul 20 03:14:26 2019 +0200 |
committer | Sijie Guo <guosijie@gmail.com> | Sat Jul 20 09:14:26 2019 +0800 |
tree | e2caf8dffb5b32fc0d0fec89df3a1cad9ddae1b9 | |
parent | b182b7478687328126a6aced27d5359fdf280e5c [diff] |
Fix log statements with incorrect placeholders ### Changes The following changes were made: - remove unused placeholders in the log statements - add missing placeholders to the log strings to show the complete information - remove unnecessary initialization of object arrays in the log statements Reviewers: Sijie Guo <None> This closes #2123 from vzhikserg/fix-log-statements
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.