[
https://issues.apache.org/jira/browse/OAK-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated OAK-410:
--------------------------------
Attachment: OAK-410.patch
Attaching a proposed patch that triggers a reindex on the initial repo content,
just before the validators&commit hooks are in place.
It's not the best solution, maybe this can help start a conversation about how
we can fix this issue.
With this in place we can even remove the "reindex, true" properties on the
index definitions.
Again the purpose of this is to have the initial content indexed so that the
query engine can leverage defined indexes from the very beginning.
> RepositoryInitializer runs before the CommitHooks are in place
> --------------------------------------------------------------
>
> Key: OAK-410
> URL: https://issues.apache.org/jira/browse/OAK-410
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Alex Parvulescu
> Attachments: OAK-410.patch
>
>
> The InitialContent installs a bunch of content nodes before the CommitHooks
> are enabled.
> This hurts the query indexes as they don't get notified about the initial
> content and cannot index/process it.
> I'm mostly referring to the Auth stuff that relies on a combo of initial
> content & queries.
> Luckily when using the PropertyIndex it does fallback to full repository
> traversal, which works (albeit slowly). Unfortunately I can't say the same
> for the lucene index).
> A bit of context here [0].
> [0]
> https://issues.apache.org/jira/browse/OAK-403?focusedCommentId=13486763&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13486763
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
