[jira] [Updated] (ZOOKEEPER-1992) backward compatibility of zoo.cfg

["Alexander Shraer (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Shraer updated ZOOKEEPER-1992:
----------------------------------------

    Attachment: final1.patch

+1 The patch looks good, thanks for the hard work Hongchao!
I made a few minor edits, mainly variable names and some changes to the test. Lets see that final1.patch passes the tests on Jenkins and then commit it.

> backward compatibility of zoo.cfg
> ---------------------------------
>
>                 Key: ZOOKEEPER-1992
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1992
>             Project: ZooKeeper
>          Issue Type: Bug
>    Affects Versions: 3.5.0
>            Reporter: Hongchao Deng
>            Assignee: Hongchao Deng
>            Priority: Blocker
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-1992-addTest.patch, ZOOKEEPER-1992-gitaddp.patch, ZOOKEEPER-1992-without-spaces.patch, ZOOKEEPER-1992-withspaces.patch, draft-2.patch, draft-3.patch, draft-4.patch, draft.patch, final.patch, final1.patch
>
>
> This issue supersedes our discussion in ZOOKEEPER-1989.
> To summarize, ZK users can seamlessly upgrade 3.4 to 3.5. But two things will happen:
> 1. the server list will be separated out as a dynamic file (the original should be backup automatically).
> 2. Client port is mandatory on reconfig. So when reconfig the server itself (its id), the client port in config file will be removed and replaced by the one in reconfig (written in dynamic file).



--
This message was sent by Atlassian JIRA
(v6.2#6252)