A bookkeeper should fallback to use v3 protocol for some types of requests if they are not implemented in v2 #2071
Labels
Comments
|
/cc @zymap |
zymap
added a commit
to zymap/bookkeeper
that referenced
this issue
May 5, 2019
--- Fixes apache#2071 *Motivation* A bookkeeper should fallback to use v3 protocol for some types of requests if they are not implemented in v2 *Modifications* - Add a client pool use v3 wire protocol - Obtain client by version
zymap
added a commit
to zymap/bookkeeper
that referenced
this issue
May 5, 2019
--- Fixes apache#2071 *Motivation* A bookkeeper should fallback to use v3 protocol for some types of requests if they are not implemented in v2 *Modifications* - Add a client pool use v3 wire protocol - Obtain client by version
sijie
pushed a commit
that referenced
this issue
May 20, 2019
…t implemented in v2 Descriptions of the changes in this PR: ### Motivation #2071 ### Changes - Add a client pool use v3 wire protocol - Obtain client by version - Currently only support `writeLac` and `readLac` Master Issue: #2071 Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2085 from zymap/compatible_protocol
|
This has been implemented and fixed by #2085 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
FEATURE REQUEST
Currently not all the features are available in v2 protocol. Such as readLac, writeLac, getBookieInfo. The gap is increasing as well. Moving forward, it is really hard to maintain what features are not available when
useV2WireProtocolis used.When a bookkeeper client is configured with
useV2WireProtocol = true, it should fallback to use v3 protocol for the types of request that v2 doesn't support. This would allow use have a fully functional client even when usinguseV2WireProtocol = true.This is a blocker for apache/pulsar#3828
For addressing the problem in apache/pulsar#3828
The text was updated successfully, but these errors were encountered: