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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/09/10 12:18:28 UTC

[jira] [Commented] (OAK-1977) ContentMirrorStoreStrategy should utilize path restriction when available

    [ https://issues.apache.org/jira/browse/OAK-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128306#comment-14128306 ] 

Thomas Mueller commented on OAK-1977:
-------------------------------------

Revision 1623964 (trunk)

This is a slightly different solution, which moves the filter logic to the PathIterator. The prefix logic is also moved there (it has to be, otherwise filtering is much more complicated). Filtering is different: instead of traversing to the required node, paths that don't match are skipped. This is slightly less efficient, but I think should work reasonably well.

> 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.3.4#6332)