You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Varun Mehrotra (JIRA)" <ji...@apache.org> on 2017/01/22 21:03:26 UTC
[jira] [Commented] (OAK-5499) IndexUpdate can do mulitple traversal
of a content tree during initial index when there are sub-root indices
[ https://issues.apache.org/jira/browse/OAK-5499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833697#comment-15833697 ]
Varun Mehrotra commented on OAK-5499:
-------------------------------------
Thanks [~catholicon] for logging this issue. Can we increase the priority of this?
> IndexUpdate can do mulitple traversal of a content tree during initial index when there are sub-root indices
> ------------------------------------------------------------------------------------------------------------
>
> Key: OAK-5499
> URL: https://issues.apache.org/jira/browse/OAK-5499
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.8
>
>
> In case we've index defs such as:
> {noformat}
> /oak:index/foo1Index
> /content
> /oak:index/foo2Index
> {noformat}
> then initial indexing process \[0] would traverse tree under {{/content}} twice - once while indexing for top-level indices and next when it starts to index newly discovered {{foo2Index}} while traversing {{/content/oak:index}}.
> What we can do is that while first diff processes {{/content}} and discovers a node named {{oak:index}}, it can actively go in that tree and peek into index defs from under it and register as required. The diff can then proceed under {{/content}} while the new indices would also get diffs (avoiding another traversal)
> \[0] first time indexing or in case {{/:async}} gets deleted or checkpoint for async index couldn't be retrieved
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)