commit | 7850554a8349cedf1d9236a242e2f7739b471bc9 | [log] [tgz] |
---|---|---|
author | odidev <odidev@puresoftware.com> | Fri Sep 11 10:31:46 2020 +0530 |
committer | GitHub <noreply@github.com> | Thu Sep 10 23:01:46 2020 -0600 |
tree | 7f48d2b96834a9ad8df8deea00e8dc0901d429c9 | |
parent | fff74dbbc3132a9e854a128d3174371e5a6fd8b0 [diff] |
Updated netty,netty-boringssl and rocksdb ### Descriptions of the changes in this PR: -Updated netty,netty-boringssl and rocksdb to latest version for aarch64 support -Updated deprecated methods of rocksdb to remove compilation warning and resolve build failure of bookkeeper-server on amd64 and aarch64 platforms as Werror flag is enabled. ### Motivation Build of the bookkeeper-server package was failing on amd64 and aarch64 platforms. ### Changes There are many methods that are marked deprecated in rocksdb, but in use by bookkeeper package. So updated those methods in bookkeeper package according to current rocksdb implementation. Also updated netty,netty-boringssl and rocksdb to latest version as they are having aarch64 support. Master Issue: #2378 Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None> This closes #2379 from odidev/bookkeeper_aarch
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.