commit | 41412bc647f94d6e13d8dde6daa3081c010d0806 | [log] [tgz] |
---|---|---|
author | Nicolò Boschi <boschi1997@gmail.com> | Fri Oct 09 17:37:44 2020 +0200 |
committer | GitHub <noreply@github.com> | Fri Oct 09 17:37:44 2020 +0200 |
tree | a4f17445998e75c4bf029249a4f98ab3c3df5eda | |
parent | 9427c8b8f89539e4098771f1367b6e8910fdb336 [diff] |
BP-42: new api list ledgers Descriptions of the changes in this PR: ### Motivation The new Client API (org.apache.bookkeeper.client.api.BookKeeper) aims to replace obsolete BookKeeper API but some features are not implemented yet, like the functionalities provided by BookKeeperAdmin. For example, it does not expose a method to list available ledgers, comparable to BookKeeperAdmin#listLedgers(). low. ### Changes - Ledgers listing - Simpler access to LedgerMetadata - Ledger id inside LedgerMetadata Master Issue: #2422 Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2423 from nicoloboschi/bp42-new-api-list-ledgers
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.