commit | 6989954e05504c345ae9e50c9c906f8291a6dc02 | [log] [tgz] |
---|---|---|
author | Rajan Dhabalia <rdhabalia@apache.org> | Fri Jan 31 04:26:16 2020 -0800 |
committer | GitHub <noreply@github.com> | Fri Jan 31 13:26:16 2020 +0100 |
tree | b4b946c39b088da698cc8d35d7a8d581575debab | |
parent | e37f3aa03ad4d1ad1e5ded2ffceac3e844e6f46e [diff] |
[CODE-STYLE] fix build failure for check-style Descriptions of the changes in this PR: ### Motivation PR Validation build is failing with below exception: ``` [ERROR] src/main/java/org/apache/bookkeeper/stream/storage/impl/cluster/ZkClusterInitializer.java:[35] (imports) ImportOrder: Import org.apache.bookkeeper.stream.storage.StorageConstants.getSegmentsRootPath appears after other imports that it should precede [ERROR] Failed to execute goal org.apache.maven.plugins:maven-checkstyle-plugin:3.0.0:check (default-cli) on project stream-storage-service-impl: You have 1 Checkstyle violation. -> [Help 1] ``` Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2258 from rdhabalia/checkZk
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.