You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Abhiraj Butala (JIRA)" <ji...@apache.org> on 2017/03/13 16:33:42 UTC
[jira] [Assigned] (ZOOKEEPER-748) zkPython's NodeExistsException
should include information about the node that exists
[ https://issues.apache.org/jira/browse/ZOOKEEPER-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhiraj Butala reassigned ZOOKEEPER-748:
----------------------------------------
Assignee: (was: Abhiraj Butala)
> zkPython's NodeExistsException should include information about the node that exists
> ------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-748
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-748
> Project: ZooKeeper
> Issue Type: Improvement
> Components: contrib-bindings
> Affects Versions: 3.3.0
> Reporter: Joseph Koshy
> Fix For: 3.5.4, 3.6.0
>
>
> Currently the code creates a {{zookeeper.NodeExistsException}} object with a string argument "node exists".
> Including the name of the node that caused the exception would be useful, in that it allows user code like the following:
> {code:title=example1}
> try:
> zookeeper.create(zh, n1, ...)
> zookeeper.create(zh, n2, ...)
> except zookeeper.NodeExistsException, n:
> print "Node \"%s\" exists." % n
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)