Drop Maven Profile -Dstream (#2233)

### Motivation

The "stream" profile enables the build of all of the additional packages regarding the 'table service'.
This profile complicates a lot every script and the Maven project.
As the stream storage service is now stable and used in production, it is better to always include those modules.
Regualar developers on bookkeeper-server module won't be affected by this change as it affects only the full build and the release process.

### Changes
Modify every pom.xml in order to enable all of the parts of the pom.xml that would be enabled with '-Dstream'.
Modify release scripts by removing references to -Dstream
Modify bin/common.sh about the auto build feature
Modify Groovy scripts for Jenkins
Do not "shade" libthrift inside Distributed Log Jar

I did not modify the website because currently the precommit validation of the website is broken


* Remove stream Maven Profile

* Delete job_bookkeeper_precommit_java11.groovy

* Delete job_bookkeeper_precommit_java8.groovy

* Delete ticktoc.sh

* Restore -DstreamTests profile

Co-authored-by: Enrico Olivelli <eolivelli@apache.org>
19 files changed
tree: 3f1d4a83cd6b161cbc31ae301beabf0d6cda81c1
  1. .github/
  2. .test-infra/
  3. bin/
  4. bookkeeper-benchmark/
  5. bookkeeper-common/
  6. bookkeeper-common-allocator/
  7. bookkeeper-dist/
  8. bookkeeper-http/
  9. bookkeeper-proto/
  10. bookkeeper-server/
  11. bookkeeper-stats/
  12. bookkeeper-stats-providers/
  13. buildtools/
  14. circe-checksum/
  15. conf/
  16. cpu-affinity/
  17. deploy/
  18. dev/
  19. docker/
  20. metadata-drivers/
  21. microbenchmarks/
  22. shaded/
  23. site/
  24. stats/
  25. stream/
  26. tests/
  27. tools/
  28. .gitignore
  29. LICENSE
  30. NOTICE
  31. pom.xml
  32. README.md
README.md

Build Status Build Status Coverage Status Maven Central

Apache BookKeeper

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:

  • WAL (Write-Ahead-Logging), e.g. HDFS NameNode.
  • Message Store, e.g. Apache Pulsar.
  • Offset/Cursor Store, e.g. Apache Pulsar.
  • Object/Blob Store, e.g. storing state machine snapshots.

Get Started

  • Concepts: Start with the basic concepts of Apache BookKeeper. This will help you to fully understand the other parts of the documentation.
  • Getting Started to setup BookKeeper to write logs.

Documentation

Developers

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.

Administrators

Contributors

Get In Touch

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.

Need Help?

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.

Contributing

We feel that a welcoming open community is important and welcome contributions.

Contributing Code

  1. See Developer Setup to get your local environment setup.

  2. Take a look at our open issues: JIRA Issues Github Issues.

  3. Review our coding style and follow our pull requests to learn about our conventions.

  4. Make your changes according to our contribution guide.

Improving Website and Documentation

  1. See Building the website and documentation on how to build the website and documentation.