[
https://issues.apache.org/jira/browse/ZOOKEEPER-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174569#comment-13174569
]
Ted Dunning commented on ZOOKEEPER-1336:
----------------------------------------
Taking the easy question first, yes, the order is implied.
Regarding the javadoc, I believe that this refers to a capability that was
removed because it turned out to be redundant after we decided to return a list.
> javadoc for multi is confusing, references functionality that doesn't seem to
> exist
> ------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1336
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1336
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.4.1
> Reporter: Patrick Hunt
>
> There's this in org.apache.zookeeper.ZooKeeper.multi(Iterable<Op>)
> {noformat}
> * Executes multiple Zookeeper operations or none of them. On success, a
> list of results is returned.
> * On failure, only a single exception is returned. If you want more
> details, it may be preferable to
> * use the alternative form of this method that lets you pass a list into
> which individual results are
> * placed so that you can zero in on exactly which operation failed and
> why.
> {noformat}
> What is the "alternate form of this method" that's being referred to? Seems
> like we should add this functionality, or at the very least update the
> javadoc. (I don't think this is referring to Transaction, although the docs
> there are pretty thin)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
