[
https://issues.apache.org/jira/browse/OAK-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-6463:
---------------------------------
Attachment: OAK-6463-v1.patch
[patch|^OAK-6463-v1.patch] for the same.
Issue here was that for any property index update PropertyIndexEditor had to
initialize NodeBuilder for all IndexStoreStrategy (which are 1 per mount). Now
if the index did not had entries for private mount at setup time (when writes
to it were allowed) then later this cases issue as on update the editor would
try to eagerly initialize the NodeBuilder for :oak:mount-<>-index node even if
no updates need to be done under that.
This patch fixes this by using a lazy builder i.e. use Supplier<NodeBuilder>
where NodeBuilder is constructed on demand. With this a mount related index
node is not created for normal index updates.
[~stillalex] Please review!
> 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)
