[
https://issues.apache.org/jira/browse/OAK-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096782#comment-14096782
]
Thomas Mueller commented on OAK-1977:
-------------------------------------
I'm currently reviewing the patch. [~catholicon], what is the use case for
_non_ filter-aware lookup, that is, why do we still need a
ContentMirrorStoreStrategy with isFilterAware set to false? Wouldn't it be
better to just _always_ use the filter if available?
> ContentMirrorStoreStrategy should utilize path restriction when available
> -------------------------------------------------------------------------
>
> Key: OAK-1977
> URL: https://issues.apache.org/jira/browse/OAK-1977
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Affects Versions: 1.0.1
> Reporter: Vikas Saurabh
> Assignee: Thomas Mueller
> Fix For: 1.1
>
> Attachments: 1977-benchmark.patch, 1977-proposed.patch
>
>
> Currently {{ContentStoreMirrorStrategy}} has a mirror of content path under
> {{:index}}. Yet, while {{query}} (and {{count}}) methods doesn't jump
> directly into restricted path.
> This would be very useful for {{PropertyIndex}} where the queries can be
> optimized by supplying a path restriction along with an indexed property
> restriction (I don't know if queries with references would use paths so much
> though)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
