[
https://issues.apache.org/jira/browse/OAK-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501853#comment-13501853
]
Jukka Zitting commented on OAK-410:
-----------------------------------
+1 Looks good, let's start with that.
I like the idea of using a branch for the initialization, and wonder if we
could go even a bit further by turning the initializer into:
{code}
public interface RepositoryInitializer {
NodeState initialize(NodeState state);
}
{code}
Things like the security initializers that depend on higher level APIs could
still construct a MemoryNodeStore starting from the given base state and use
that to build the returned state.
> 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
> Fix For: 0.6
>
> Attachments:
> 0001-OAK-410-RepositoryInitializer-runs-before-the-Commit.patch,
> OAK-410.patch, OAK-410-v3.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
