[jira] [Commented] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()

2017-10-09 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197016#comment-16197016
 ] 

Julian Reschke commented on OAK-6782:
-

trunk: [r1811575|http://svn.apache.org/r1811575]


> 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, 1.7.9
>
>
> {{remove(Collection collection, Map> 
> 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)

[jira] [Commented] (OAK-6782) RDBDocumentStore: inconsistent handling of cache invalidation on remove()

2017-10-09 Thread Julian Reschke (JIRA) 

[ 
https://issues.apache.org/jira/browse/OAK-6782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196852#comment-16196852
 ] 

Julian Reschke commented on OAK-6782:
-

Looking at the MongoDS variant shows that we always invalidate after talking to 
the persistence; and so so in the {{finally}} block. Will adjust RDB to do the 
same.

> 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
>
> {{remove(Collection collection, Map> 
> 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)