[ZOOKEEPER-510] zkpython lumps all exceptions as IOError, needs specialized exceptions for KeeperException types

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.0
• Fix Version/s: 3.2.2, 3.3.0
• Component/s: contrib-bindings
• Hadoop Flags: Reviewed
• Assignee: Henry Robinson
• Reporter: Patrick D. Hunt
• Created: 19/Aug/09 21:13
• Updated: 26/Mar/10 17:25
• Resolved: 14/Oct/09 00:14

Description

The current zkpython bindings always throw "IOError("text")" exceptions, even for ZK specific exceptions such as NODEEXISTS. This makes it difficult (error prone) to handle exceptions in python code. You can't easily pickup a connection loss vs a node exists for example. Of course you could match the error string, but this seems like a bad idea imo.

We need to add specific exception types to the python binding that map directly to KeeperException/java types. It would also be useful to include the information provided by the KeeperException (like path in some cases), etc... as part of the error thrown to the python code. Would probably be a good idea to stay as close to java api as possible wrt mapping the errors.