commit | fe25574edc80f7c53141a0bd610bcf26d6b9b8d8 | [log] [tgz] |
---|---|---|
author | dmercuriali <mercurialiden@gmail.com> | Thu May 07 09:23:04 2020 +0200 |
committer | GitHub <noreply@github.com> | Thu May 07 09:23:04 2020 +0200 |
tree | bc9ca9d04ef10ac2c65b98185480a76cdd097813 | |
parent | 34d35f033e1ef099e60ac75a9d59aecc6c5a2001 [diff] |
Issue #2106: Update ZookKeeper dependency to 3.5.7 Descriptions of the changes in this PR: Updated ZooKeeper dependency from 3.4.13 to 3.5.7 Excluded transitive dependency to netty-all. Updated maven-shade-pluging configuration in 'distributedlog-core-shaded' project. Package 'org.apache.jute' was moved to a ZooKeeper dependency (org.apache.zookeeper:zookeeper-jute), so i added the artifact to the artifactSet. Updated license files: - updated Zookeeper to 3.5.7 - removed Jline 2.11 - removed Netty 3.10.1 - added Zookeeper-jute 3.5.7 Master Issue: #2106 Reviewers: Matteo Minardi <minardi.matteo@hotmail.it>, Enrico Olivelli <eolivelli@gmail.com>, Jia Zhai <zhaijia@apache.org> This closes #2112 from dmercuriali/fix/#2106-update-zookeeper, closes #2106
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.