[
https://issues.apache.org/jira/browse/ZOOKEEPER-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518624#comment-15518624
]
Arshad Mohammad commented on ZOOKEEPER-2276:
--------------------------------------------
Async multi API does process the result and also it does not throw exception.
Result is processed in the callback handler
I think the logic to find path of failed transaction should be written in the
callback handler. So no changed with respect to async multip API.
submitting the res-based patch
> Multi operation failure does not include path in KeeperException
> -----------------------------------------------------------------
>
> Key: ZOOKEEPER-2276
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2276
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.5.0
> Environment: Suse 11 SP3
> Reporter: neha
> Assignee: Arshad Mohammad
> Priority: Minor
> Fix For: 3.5.3
>
> Attachments: ZOOKEEPER-2276-01.patch
>
>
> With normal create operation, the path of the failed node is displayed in
> KeeperException but this is not the case when create operation is through
> multi api
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
