[
https://issues.apache.org/jira/browse/OAK-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517012#comment-14517012
]
Chetan Mehrotra edited comment on OAK-2599 at 4/30/15 5:48 AM:
---------------------------------------------------------------
Had a discussion with [~tmueller] and following needs to be worked upon
Key concern is mismatch between PathRestriction and Index path filter.
Following scenarios need to be honored
# Query does not have path restriction, index has path filter - Index should be
used
# Query has a path restriction, path restriction match index filter - Index
should be used
# Query has a path restriction, path restriction does not match index filter -
Index should not be used. This might result in traversal happening for such
queries
# Query has a path restriction, path restriction does not match index filter,
{{forceIndexOnPathRestrictionMismatch}} set - Index should be used. Potentially
logging a warning
-Further PathFilter can for now be moved to oak-lucene till it gets stable.
Once we stablize the concept there we can promote it to oak-core for other
index implementation to make use of that- Not required. PathFilter can remain
in oak-core
was (Author: chetanm):
Had a discussion with [~tmueller] and following needs to be worked upon
Key concern is mismatch between PathRestriction and Index path filter.
Following scenarios need to be honored
# Query does not have path restriction, index has path filter - Index should be
used
# Query has a path restriction, path restriction match index filter - Index
should be used
# Query has a path restriction, path restriction does not match index filter -
Index should not be used. This might result in traversal happening for such
queries
# Query has a path restriction, path restriction does not match index filter,
{{forceIndexOnPathRestrictionMismatch}} set - Index should be used. Potentially
logging a warning
Further PathFilter can for now be moved to oak-lucene till it gets stable. Once
we stablize the concept there we can promote it to oak-core for other index
implementation to make use of that
> Allow excluding certain paths from getting indexed for particular index
> -----------------------------------------------------------------------
>
> Key: OAK-2599
> URL: https://issues.apache.org/jira/browse/OAK-2599
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core, query
> Reporter: Chetan Mehrotra
> Labels: performance
> Fix For: 1.3.0
>
> Attachments: OAK-2599-1.patch
>
>
> Currently an {{IndexEditor}} gets to index all nodes under the tree where it
> is defined (post OAK-1980). Due to this IndexEditor would traverse the whole
> repo (or subtree if configured in non root path) to perform reindex.
> Depending on the repo size this process can take quite a bit of time. It
> would be faster if an IndexEditor can exclude certain paths from traversal
> Consider an application like Adobe AEM and an index which only index
> dam:Asset or the default full text index. For a fulltext index it might make
> sense to avoid indexing the versionStore. So if the index editor skips such
> path then lots of redundant traversal can be avoided.
> Also see http://markmail.org/thread/4cuuicakagi6av4v
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
