commit | 87981d420d0ae9d472d4e92b7abc145069e17e61 | [log] [tgz] |
---|---|---|
author | Sijie Guo <sijie@apache.org> | Sun Mar 29 17:14:05 2020 -0700 |
committer | GitHub <noreply@github.com> | Sun Mar 29 17:14:05 2020 -0700 |
tree | c50b94e961dbf62ca5b15ff50ed36fe3280d7664 | |
parent | e482a125429d6b29382ea56b793daa5447927655 [diff] |
Unable to enable TLS if using v2 protocol Descriptions of the changes in this PR: *Motivation* TLS is enabled using `startTLS` but the `startTLS` is a v3 protobuf request. So if the client is configured to use v2 protocol, the client is not able to decode `startTLSResponse`. *Modifications* This change is to improve the v2 protocol response handling for handling `startTLS` response. Reviewers: Enrico Olivelli <eolivelli@gmail.com> This closes #2300 from sijie/fix_tls_v2_protocol
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.