commit | 0fe624819b56951daf1a98a78651e981b7629042 | [log] [tgz] |
---|---|---|
author | lamber-ken <lamberken@apache.org> | Wed May 27 14:15:52 2020 +0800 |
committer | GitHub <noreply@github.com> | Wed May 27 08:15:52 2020 +0200 |
tree | dc98f3cd6046ebdd3ad1d5c430b1e22664702f62 | |
parent | 637bfa756ddba08bf5f67fc2d45124afd5dbc0bc [diff] |
[CLEAN] remove duplicate property key in log4j.properties ### Motivation 1. Fix duplicate key in log4j.properties 2. `http` to `https` in `README` ### Changes ![image](https://user-images.githubusercontent.com/20113411/82162451-369ef880-98d7-11ea-9217-777721bba545.png) ![image](https://user-images.githubusercontent.com/20113411/82162816-d2c9ff00-98d9-11ea-967e-53646d351753.png) Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2334 from lamber-ken/clean-log
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.