commit | 616d4c15bf85fcbe3fdfa039c8da875cc94e81f7 | [log] [tgz] |
---|---|---|
author | Sijie Guo <guosijie@gmail.com> | Fri Dec 14 09:43:33 2018 +0800 |
committer | GitHub <noreply@github.com> | Fri Dec 14 09:43:33 2018 +0800 |
tree | 9f7489f1f91dfdff508d94fc80d1f190ba2fea32 | |
parent | 7e047d93fc9b4407667c7a5d858dcd88a046598f [diff] |
BP-37: Improve configuration management for better documentation Descriptions of the changes in this PR: *Motivation* One common task in developing bookkeeper is to make sure all the configuration settings are well documented, and the configuration file we ship in each release is in-sync with the code itself. However maintaining things in-sync is non-trivial. This proposal is exploring a new way to manage configuration settings for better documentation. Master Issue: #1867 Reviewers: Matteo Merli <mmerli@apache.org>, Enrico Olivelli <eolivelli@gmail.com>, Jia Zhai <None> This closes #1868 from sijie/bp37_conf_documentation
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.