[
https://issues.apache.org/jira/browse/OAK-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091471#comment-16091471
]
Alex Deparvu commented on OAK-6463:
-----------------------------------
very interesting fix! I'm wondering if the 'index' supplier should not be
wrapped into a {{Suppliers.memoize}} call so you'd get the same {{NodeBuilder}}
instance on each {{.get()}} call. In the current form it will return a new
builder on each call and while it will still probably work, I'm a bit worried
about the perf impact.
> Property index update fails in composite NodeStore setup
> --------------------------------------------------------
>
> Key: OAK-6463
> URL: https://issues.apache.org/jira/browse/OAK-6463
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: composite, property-index
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 1.8
>
> Attachments: OAK-6463-v1.patch
>
>
> In a CompositeNodeStore setup involving 1 read only mount a commit involving
> update of property index may fail even if the commit does not update content
> under read only paths
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
