[ https://issues.apache.org/jira/browse/OAK-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743185#comment-14743185 ]
Elemer Kisch commented on OAK-3366: ----------------------------------- [~chetanm] Yepp, thank you for clarifying. > Property indexes reindex flag getting reset to true at startup > -------------------------------------------------------------- > > Key: OAK-3366 > URL: https://issues.apache.org/jira/browse/OAK-3366 > Project: Jackrabbit Oak > Issue Type: Bug > Components: jcr > Reporter: Chetan Mehrotra > Assignee: Chetan Mehrotra > Fix For: 1.3.6 > > Attachments: OAK-3366-01.patch, OAK-3366.patch > > > At times it is seen that {{reindex}} flag for property indexes is getting > reset to true. As per analysis by [~alex.parvulescu] it happens due to the > order in which repository gets started and PropertyIndexEditorProvider gets > registered. > If the editor is registered after repository got started then _missing index > provider_ for the 'property' type will silently set *all* the existing > property index definitions reindex flags to true. > After some offline discussion it was decided that proper fix here would be to > ensure that repository is only started *after* property index editor gets > registered. This would ensure that the whiteboard tracker would be opened in > that activate itself after the provider is registered and it is ensured that > if a tracker is opened it gets access to already registered services without > any delay. This would avoid any scenario where commit happens without any > property index editor being present -- This message was sent by Atlassian JIRA (v6.3.4#6332)