Google Git
Sign in
apache / bookkeeper / 2ff7ca5af53f59f2ba11391292016554ace35720
commit2ff7ca5af53f59f2ba11391292016554ace35720[log] [tgz]
authorEnrico Olivelli <eolivelli@gmail.com>Sat Jan 04 14:10:31 2020 +0100
committerGitHub <noreply@github.com>Sat Jan 04 14:10:31 2020 +0100
tree53e8b8b0f1e51c40a4c0c2a008bef852af69dafb
parent2bbf58e0168df000db1712a84acaecf61d00c347 [diff]
Account Apache Thrift and Http Client files in LICENSE files - Fix build on Travis

fixes #2227

Descriptions of the changes in this PR:
- Account Thrift and Http client in LICENSE files.
- Force using Maven 3.6.3 in MacOSx builds on Travis
- Test only with -Dstream profile


### Motivation

Those files are inside the binary packages but they are not taken into account in LICENSE file.
Travis started to report errors when Travis updated Maven version to 3.6.2 in Linux machines, MaxOSx machines are still with 3.3.9 and the build does not bundle all of the needed jars ! 

Master Issue: #2227 




Reviewers: Jia Zhai <zhaijia@apache.org>, Sijie Guo <None>

This closes #2228 from eolivelli/fix/license-files
5 files changed
tree: 53e8b8b0f1e51c40a4c0c2a008bef852af69dafb
  1. .github/
  2. .test-infra/
  3. .travis_scripts/
  4. bin/
  5. bookkeeper-benchmark/
  6. bookkeeper-common/
  7. bookkeeper-common-allocator/
  8. bookkeeper-dist/
  9. bookkeeper-http/
  10. bookkeeper-proto/
  11. bookkeeper-server/
  12. bookkeeper-stats/
  13. bookkeeper-stats-providers/
  14. buildtools/
  15. circe-checksum/
  16. conf/
  17. cpu-affinity/
  18. deploy/
  19. dev/
  20. docker/
  21. metadata-drivers/
  22. microbenchmarks/
  23. shaded/
  24. site/
  25. stats/
  26. stream/
  27. tests/
  28. tools/
  29. .gitignore
  30. .travis.yml
  31. LICENSE
  32. NOTICE
  33. pom.xml
  34. 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.