commit | 0c841862b547374541815d9dd9dfb4488b49ab44 | [log] [tgz] |
---|---|---|
author | Nicolò Boschi <boschi1997@gmail.com> | Thu Oct 29 11:28:36 2020 +0100 |
committer | GitHub <noreply@github.com> | Thu Oct 29 11:28:36 2020 +0100 |
tree | 48ad977c42627eed1812e066f09e0547db23b6d7 | |
parent | 71f8e160b2e8cd16cb18bc186fcd67887150403e [diff] |
BP-42: New Client API - list ledgers Implementation of BP-42 ### Motivation Enhance new client API, added methods for - listing ledgers - access to ledger metadata ### Changes - Added new interfaces in "api" client package for ledgers listing - Added new method `getLedgerMetadata(long ledgerId)` to BookKeeper interface - Added `getLedgerId()` to LedgerMetadata type -- Ledger metadata ser/deser are not changed since ledgerId is not stored inside ZK data node Updated all tests using `LedgerMetadataBuilder` because ledgerId is now required in order to call `build()` method Master Issue: #2422 Reviewers: Jia Zhai <zhaijia@apache.org>, Enrico Olivelli <eolivelli@gmail.com> This closes #2457 from nicoloboschi/fix/2422/bp-42-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.