commit | 9ad191ca0fc0bf2eaeabdc5dc796c8c53fe390a8 | [log] [tgz] |
---|---|---|
author | Kieran Gorman <kierangorman@monzo.com> | Mon Feb 25 09:20:34 2019 +0000 |
committer | Sijie Guo <guosijie@gmail.com> | Mon Feb 25 17:20:34 2019 +0800 |
tree | 7c262e42ff348ff1745bd5425dc4428d6b4123ae | |
parent | 9c14476422ee865769152917405607bd330046fa [diff] |
[DOC] popover for 'striped' as well as 'striping' Adds a popover term for 'striped' to match 'striping'. ### Motivation <img width="817" alt="screen shot 2019-02-19 at 14 08 07" src="https://user-images.githubusercontent.com/1994486/53020896-ddd07e00-344f-11e9-9327-7beb380515d7.png"> The first "link" text has no pop-over, but the second does. ### Changes Just copies the pop-over for striping. It seems inelegant vs. allowing multiple pop-over terms to refer to the same HTML fragment rather than being 1-1, but also is a straightforward and unobtrusive change. Master Issue: (no issue) Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #1951 from kjgorman/striped-popover
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.