[ZOOKEEPER-253] documentation of DataWatcher state transition is misleading regarding auto watch reset on reconnect

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0, 3.0.1
• Fix Version/s: 3.1.0
• Component/s: documentation
• Hadoop Flags: Reviewed
• Assignee: Patrick D. Hunt
• Reporter: Patrick D. Hunt
• Created: 11/Dec/08 18:45
• Updated: 13/Feb/09 21:18
• Resolved: 28/Jan/09 00:47

Description

the example code has

case SyncConnected:
// Everything is happy. Lets kick things off
// again by checking the existence of the znode
break;

this is misleading - it should indicate that the watches are automatically reset and therefor no call to exists is necessary

also fix this in the same doc (looks like its old detail, no longer valid), indicate that autoreset will happen on reconnect.

If the client-side ZooKeeper libraries can reestablish the communication channel to ZooKeeper, DataMonitor simply kicks everything off again with the call to ZooKeeper.exists(). If it gets an event for a znode, it calls ZooKeeper.exists() to find out what has changed.