You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2017/10/09 12:53:00 UTC
[jira] [Updated] (OAK-6782) RDBDocumentStore: inconsistent handling
of cache invalidation on remove()
[ https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated OAK-6782:
--------------------------------
Labels: candidate_oak_1_0 candidate_oak_1_2 candidate_oak_1_4 candidate_oak_1_6 (was: )
> RDBDocumentStore: inconsistent handling of cache invalidation on remove()
> -------------------------------------------------------------------------
>
> Key: OAK-6782
> URL: https://issues.apache.org/jira/browse/OAK-6782
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: documentmk, rdbmk
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, candidate_oak_1_6
> Fix For: 1.8
>
>
> {{remove(Collection<T> collection, Map<String, Map<Key, Condition>> toRemove)}} invalidates the cache after talking to the DB. The other variants do it before.
> [~mreutegg] - this was added for OAK-2804 - do you recall whether there was a specific reason to do it like that?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)