[
https://issues.apache.org/jira/browse/ZOOKEEPER-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484256#comment-13484256
]
Jimmy Xiang commented on ZOOKEEPER-1568:
----------------------------------------
For our use case, there is no dependency issue. "Batch" is what we want.
Another benefit is that we will get less ZK events. This may not be obvious.
But we will do get less ZK events. For example, for a bunch of create
operations, if we do it one by one, once we get a nodeChildrenChanged event, we
will watch it again, so we will get another one for the next create operation.
If they are batched, after we get the first nodeChildrenChanged event, when we
watch it again, most likely, other nodes are already created, so we will get
less events, which is good.
> multi should have a non-transaction version
> -------------------------------------------
>
> Key: ZOOKEEPER-1568
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1568
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Jimmy Xiang
>
> Currently multi is transactional, i.e. all or none. However, sometimes, we
> don't want that. We want all operations to be executed. Even some
> operation(s) fails, it is ok. We just need to know the result of each
> operation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
