[
https://issues.apache.org/jira/browse/OAK-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103833#comment-14103833
]
Thomas Mueller commented on OAK-1977:
-------------------------------------
I'm trying to apply the patch, but I ran into some problems. Just applying the
patch would make the tests pass, but I think this is because we don't have
enough tests... So I try to make the patch more generic (not use the
"isFilterAware" / "shouldDescendDirectly" flags), which should work as well in
_theory_. But it doesn't work in practise. There is some unexpected behavior in
PathIterator in case the shouldDescendDirectly is set, which would make some
"ordered index" tests fail. In theory the test shouldn't fail. So I'm still
investigating. I'm sorry for the delay!
> 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, 1.0.5
>
> 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)
