So I picked up CURATOR-160 from the list. What I have in mind is creating a 3.x branch (as I think that we generally agree on this) and then add the required DSL on the curator framework to support the reconfig and getconfig methods.
As a next step we need to decide how we will handle internally the reconfiguration of zookeeper. Personally I like the idea of an EnsembleProvider implementation. Thoughts? On Sat, Nov 1, 2014 at 6:29 PM, Jordan Zimmerman <[email protected]> wrote: > FYI > > I’ve created a container Jira for ZK 3.5.0 subtasks: > > https://issues.apache.org/jira/browse/CURATOR-159 > > > On November 1, 2014 at 11:25:35 AM, Jordan Zimmerman > ([email protected]) wrote: > > I think we should identify the tasks, create Jiras, etc. Then figure out the > best path from there. So, in that spirit, let’s begin. > > Major new features in 3.5.x that Curator needs to handle in some way: > > * Dynamic Reconfig > * Remove Watches > * Local Session > > Here is the current 3.5.x release notes page. Is there anything else from > here that Curator should handle? > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12316644 > > -Jordan > > > On November 1, 2014 at 11:21:35 AM, Ioannis Canellos ([email protected]) > wrote: > > Is anyone working on this? I could spend some time on zk 3.5.0. > > -- > Ioannis Canellos > > Blog: http://iocanel.blogspot.com > Twitter: iocanel -- Ioannis Canellos Blog: http://iocanel.blogspot.com Twitter: iocanel
