[
https://issues.apache.org/jira/browse/OAK-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-1678:
---------------------------
Fix Version/s: (was: 1.1)
1.1.0
> document atomicity of DS.remove(collection, keys)
> -------------------------------------------------
>
> Key: OAK-1678
> URL: https://issues.apache.org/jira/browse/OAK-1678
> Project: Jackrabbit Oak
> Issue Type: Task
> Reporter: Julian Reschke
> Assignee: Marcel Reutegger
> Labels: documentation
> Fix For: 1.1.0
>
>
> [~mreutegg]
> I believe it's best effort (looking at the MongoDB impl), but it would be
> good to clarify.
> In particular, should the operation abort then one removal failed, or keep
> going? What's the expectation when a document doesn't exist?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
