commit | 52330277565021c9d30d268cefee3e2bad1db5ae | [log] [tgz] |
---|---|---|
author | Yang Yang <yyang@streamnative.io> | Wed May 27 14:17:16 2020 +0800 |
committer | GitHub <noreply@github.com> | Wed May 27 08:17:16 2020 +0200 |
tree | 702f29753595f0f2c3d497160076d69b2f95aa3c | |
parent | 0fe624819b56951daf1a98a78651e981b7629042 [diff] |
ISSUE #2311: Adds support to decode metadata in the API that list ledgers Descriptions of the changes in this PR: ### Motivation The current list ledgers API output the metadata in a serialized binary format, which is not friendly to human operators and external tools, and is not consistent with the output of the [API that gets the metadata](https://bookkeeper.apache.org/docs/4.9.2/admin/http/#endpoint-apiv1ledgermetadataledger_idledger_id). ### Changes The PR adds a parameter called `decode_meta`, and output the ledger metadata in decoded format when the parameter presents and the value of it is 'true'. Master Issue: https://github.com/apache/bookkeeper/issues/2311 Reviewers: Sijie Guo <None>, Enrico Olivelli <eolivelli@gmail.com> This closes #2312 from fantapsody/decode_metadata, closes #2311
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.