Hadoop QA commented on ZOOKEEPER-496:
-1 overall. Here are the results of testing the latest attachment
against trunk revision 896800.
+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
+1 findbugs. The patch does not introduce any new Findbugs warnings.
-1 release audit. The applied patch generated 207 release audit warnings
(more than the trunk's current 200 warnings).
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Release audit warnings:
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.patch
> Original Estimate: 168h
> Remaining Estimate: 168h
> zktreeutil - Zookeeper Tree Data Utility
> Author: Anirban Roy
> Organization: Yahoo Inc.
> zktreeutil program is intended to manage and manipulate zk-tree data quickly,
> ciently and with ease. 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: The whole/partial ZK-tree is exported into a XML file. This helps in
> capturing a current snapshot of the data for backup/analysis. For a subtree
> export, one need to specify the path to the ZK-subtree with proper option.
> IMPORT: The ZK-tree can be imported from XML into ZK cluster. This helps in
> the new ZK cluster with static configuration. The import can be non-intrusive
> making only the additions in the existing data. The import of subtree is also
> possible by optionally providing the path to the ZK-subtree.
> DIFF: Creates a diff between live ZK data vs data saved in XML file. Diff can
> some ZK-tree branches (possibly dynamic data) on reading the optional ignore
> from XML file. Diffing on a ZK-subtree achieved by providing path to
> ZK-subtree with
> diff command.
> UPDATE: Make the incremental changes into the live ZK-tree from saved XML,
> lly after running the diff.
> DUMP: Dumps the ZK-tree on the standard output device reading either from
> live ZK
> server or XML file. Like export, ZK-subtree can be dumped with optionaly
> providing the path to the ZK-subtree, and till a certain depth of the
> The exported ZK data into XML file can be shortened by only keeping the
> static ZK
> nodes which are required to prime a cluster. The dynamic zk nodes (created
> fly) can be ignored by setting a 'ignore' attribute at the root node of the
> subtree (see tests/zk_sample.xml), possibly deleting all inner ZK nodes under
> Once ignored, the whole subtree is ignored during DIFF, UPDATE and WRITE.
This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.