commit | 73f36a2272ef061444fcb871976ef89c5ca9ded8 | [log] [tgz] |
---|---|---|
author | Like <like_0903@163.com> | Sat Mar 02 23:20:53 2019 +0800 |
committer | Sijie Guo <guosijie@gmail.com> | Sat Mar 02 23:20:53 2019 +0800 |
tree | 38f7e31f3b64d59797d415e0189a7b5b4fde2304 | |
parent | b67e8b262e3dbf77a7ef5f13c2e22bd191c85d00 [diff] |
Use automatic resource management to close streams We can use automatic resource management introduced in java 7, which makes code shorter. Reviewers: Sijie Guo <sijie@apache.org> This closes #1958 from liketic/use-resource
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.