commit | 6866b519001b79431a4fe8b4d5c4f6196632a661 | [log] [tgz] |
---|---|---|
author | Ankur Jain <ankurjain.v@flipkart.com> | Thu Dec 24 04:53:30 2020 +0530 |
committer | GitHub <noreply@github.com> | Wed Dec 23 15:23:30 2020 -0800 |
tree | 87160d8c6a0f1e43604457bfbf92bfb5dcefb75a | |
parent | f2dcaff3a087737644a08e62ddd1062fd143e589 [diff] |
ISSUE #2522: Update jcommander from 1.48 to 1.78 Descriptions of the changes in this PR: ### Motivation Certain bookkeeper shell commands when bookkeeper is bundled with pulsar because of conflicting jcommander versions ### Changes Updates jcommander to 1.78, same as pulsar. Master Issue: #2522 Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2523 from anvinjain/jcmd-1.78-update, closes #2522
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.