This change here doesn't change the behavior of bookkeeper as it doesn't use any new API introduced in 3.5. So ideally you can use 3.4 client and there is no problem. (We actually used to have shim layer to support both 3.3, 3,4 and 3.5)
- Sijie On Mon, Nov 21, 2016 at 2:52 PM, Venkateswara Rao Jujjuri <jujj...@gmail.com > wrote: > Does this make everyone to upgrade if we start making use of 3.5 API? > > On Mon, Nov 21, 2016 at 2:01 PM, ASF GitHub Bot (JIRA) <j...@apache.org> > wrote: > > > > > [ https://issues.apache.org/jira/browse/BOOKKEEPER-970? > > page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel& > > focusedCommentId=15684860#comment-15684860 ] > > > > ASF GitHub Bot commented on BOOKKEEPER-970: > > ------------------------------------------- > > > > Github user sijie commented on the issue: > > > > https://github.com/apache/bookkeeper/pull/79 > > > > @eolivelli yes. we used the new 3.5 API (e.g. asyncMulti and > > removeWatches) in DL. > > > > > > > Bump zookeeper version to 3.5 > > > ----------------------------- > > > > > > Key: BOOKKEEPER-970 > > > URL: https://issues.apache.org/ > > jira/browse/BOOKKEEPER-970 > > > Project: Bookkeeper > > > Issue Type: Improvement > > > Components: bookkeeper-client, bookkeeper-server > > > Reporter: Sijie Guo > > > Assignee: Sijie Guo > > > Fix For: 4.5.0 > > > > > > > > > in DL, we need to leverage the asynchronous version of 'multi' in > > zookeeper. so this jira is to bump the zookeeper version to 3.5 to > support > > async multi. > > > > > > > > -- > > This message was sent by Atlassian JIRA > > (v6.3.4#6332) > > > > > > -- > Jvrao > --- > First they ignore you, then they laugh at you, then they fight you, then > you win. - Mahatma Gandhi >
