commit | 865919788ab3fa422b109acb53a44ff95e19801e | [log] [tgz] |
---|---|---|
author | zhaijack <zhaijia03@gmail.com> | Sun Aug 13 21:54:08 2017 -0700 |
committer | Sijie Guo <sijie@apache.org> | Sun Aug 13 23:52:29 2017 -0700 |
tree | 744aa716a3a03d014666c4459c258f5b8d0d845e | |
parent | 0ed116f4f3e7f74e45bb96a4c5aee5c11a708ecc [diff] |
ISSUE #441: fix typos Descriptions of the changes in this PR: Fix typos in docker readme. "Apache ZooKeeper is a software project of the Apache Software Foundation" -> "Apache Bookkeeper is a software project of the Apache Software Foundation" "bookkepeer servers" -> "bookkeeper servers" "The client only need to connect to a Zookkeeper server in the ensamble" -> "The client only need to connect to a Zookeeper server in the ensemble" typo of other place: bookeeper -> bookkeeper wile -> while acknoledge -> acknowledge Author: zhaijack <zhaijia03@gmail.com> Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #442 from zhaijack/issue_441, closes #441 (cherry picked from commit e988a3cb876b5939e103e36b985ddab05173569c) Signed-off-by: Sijie Guo <sijie@apache.org>
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 scenerios:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continous 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 developement 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.