You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "TisonKun (JIRA)" <ji...@apache.org> on 2019/02/26 08:13:00 UTC
[jira] [Resolved] (ZOOKEEPER-3289) Throw KeeperException with path
in DataTree operations
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
TisonKun resolved ZOOKEEPER-3289.
---------------------------------
Resolution: Not A Problem
See ZOOKEEPER-3290 for the origin user problem and analysis.
> Throw KeeperException with path in DataTree operations
> ------------------------------------------------------
>
> Key: ZOOKEEPER-3289
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3289
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.5.4, 3.4.13
> Reporter: TisonKun
> Priority: Major
> Fix For: 3.5.5, 3.4.14
>
>
> Currently, if ZooKeeper delete a znode that does not exist. It throws a {{KeeperException.NoNodeException}} without path message. It causes difficulty when user debug with ZooKeeper. For example,
> Assume we try to do a transaction(with Curator encapsulation)
> {code:java}
> client.inTransaction()
> .check().forPath(path1).and()
> .delete().forPath(path2).and()
> .commit()
> {code}
> if the statement throw an exception {{KeeperException.NoNodeException}} without path information, we can hardly know that it failed at {{check}} or {{delete}}.
> Thus I propose throws KeeperException with path in DataTree operations. We can achieve this without burden.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)