Hadoop QA commented on ZOOKEEPER-496:

-1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 802964.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    -1 release audit.  The applied patch generated 183 release audit warnings 
(more than the trunk's current 176 warnings).

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
Release audit warnings: 
Findbugs warnings: 
Console output: 

This message is automatically generated.

> zookeeper-tree utility for export, import and incremental updates
> -----------------------------------------------------------------
>                 Key: ZOOKEEPER-496
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-496
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: contrib
>         Environment: RHEL 4.6, libxml2
>            Reporter: Anirban Roy
>            Assignee: Anirban Roy
>             Fix For: 3.3.0
>         Attachments: zktreeutil.diff
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> I propose and plan to develop a ZK-tree utility for managing cluster data (ZK 
> tree) quickly and efficiently. The utility operates on free-form ZK-tree and 
> hence can be used for any cluster managed by Zookeeper. Here are the basic 
> functionalities -
> Export ZK-tree: The whole ZK-tree is exported into a XML file. This helps in 
> capturing a current snapshot of the data for backup/analysis. In addition, 
> the data can be dumped as tree-like text format which is easily readable.
> Import ZK-tree: The ZK-tree can be imported from XML into ZK cluster. This 
> helps in priming the new ZK cluster with static configuration. The import can 
> be non-intrusive by making only the additions in the existing data.
> Diff ZK-tree: Creates a diff between live ZK data vs data saved in XML file. 
> Diff can ignore some ZK-tree branches (possibly dynamic data) on reading the 
> flag from XML file.
> Update ZK-tree: Make the incremental changes into the live ZK-tree from saved 
> XML, essentially after running the diff.
> Thanks
> Anirban

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to