| commit | e7dd19bb52d0654006decb383cb35ffcde928990 | [log] [tgz] |
|---|---|---|
| author | Enrico Olivelli <eolivelli@gmail.com> | Mon Jan 06 08:10:12 2020 +0100 |
| committer | GitHub <noreply@github.com> | Mon Jan 06 08:10:12 2020 +0100 |
| tree | e05110afdf78768298136b7a8705ea5eed2cce98 | |
| parent | 2ff7ca5af53f59f2ba11391292016554ace35720 [diff] |
Remove Twitter Libraries - Twitter Stats Providers - Twitter Http Server Descriptions of the changes in this PR: - Drop all stats providers used only by Twitter and Twitter Http server - Fix BookKeeper Server packaging, it did not include Netty epoll transport Linux binding (no .so file) - Adapt license stuff accordingly - Drop third party libs needed by Twitter stuff, most notably: Scala runtime and Netty 3.10 ### Motivation Those modules are apparently no more in use and especially they are no more mantained. It is better to remove them, the code is still on git, but we won't be building it any more or bundling useless third party libraries in our releases. ### Changes - remove twitter stats providers - remove twitter http server - adjust LICENSE file for binary distribution (bookkeeper-all) - fix pom.xml files - remove -Dtwitter from release files - remove -Dtwitter from bin/common.sh - remove other links to Twitter stuff in current documentation Master Issue: #<master-issue-number> Reviewers: Dave Rusek <dave.rusek@gmail.com>, Jia Zhai <zhaijia@apache.org>, Sijie Guo This closes #2232 from eolivelli/fix/drop-twitter-stuff
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.