commit | 92f75da3f8711cb98eda2f435bbd57ffe67e87b7 | [log] [tgz] |
---|---|---|
author | Yong Zhang <zhangyong1025.zy@gmail.com> | Mon Mar 09 19:30:00 2020 +0800 |
committer | GitHub <noreply@github.com> | Mon Mar 09 12:30:00 2020 +0100 |
tree | fed4fc194620b98b605e0d038dfeb5b939c572da | |
parent | 21e0e2f9489be85542c882e5aa41a9a7c67ba827 [diff] |
Fixes vertx can not receive the request body --- *Motivation* Vertx can not receive the request body so that the REST API can not work well if you have a request with body. *Modifications* - Add body handler for the vertx http service *Verify this change* - Pass the test `testHttpMethodsWithBody` Descriptions of the changes in this PR: ### Motivation (Explain: why you're making that change, what is the problem you're trying to solve) ### Changes (Describe: what changes you have made) Master Issue: #<master-issue-number> Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2241 from zymap/fix-can-not-read-body
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.