[
https://issues.apache.org/jira/browse/OAK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16200239#comment-16200239
]
Julian Reschke commented on OAK-6797:
-------------------------------------
Well. Yes... This is because we use these conditions in several places
(conditional update and remove). The different DS implementations evaluate
those conditions in different ways:
- MemoryDS always uses the same checker method
- MongoDS (IMHO) always passes the condition to Mongo
- RDBDS has a mix of both
>From a systematic point of view, it's strange that same conditions work on
>non-revision properties while others do not. It would probably be best to be
>consistent, and have test coverage for that for the DS update operation.
For the conditional remove we could then profile what we want to require (and
have test coverage for that as well, so tha tthe impls stay in sync).
[~mreutegg] - makes sense?
> DocumentStore conditional remove: EXISTS on non-revision property?
> ------------------------------------------------------------------
>
> Key: OAK-6797
> URL: https://issues.apache.org/jira/browse/OAK-6797
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: documentmk
> Reporter: Julian Reschke
> Priority: Minor
> Attachments: OAK-6797.diff
>
>
> Implementations currently differ in whether the "Exists" condition works on a
> non-revision property.
> (RDBDS and MongoDS seem to support it, while MemoryDS does not).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
