Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <708123.1187614650668.JavaMail.jira@brutus>
Date: Mon, 20 Aug 2007 05:57:30 -0700 (PDT)
From: "Christoph Kiehl (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1066) Exclude system index for queries that
 restrict the result set to nodetypes not availble in the "jcr:system"
 subtree
In-Reply-To: <16232565.1187278650496.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christoph Kiehl updated JCR-1066:
---------------------------------

    Attachment: patch.txt

rep:system was still missing

> Exclude system index for queries that restrict the result set to nodetypes not availble in the "jcr:system" subtree
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCR-1066
>                 URL: https://issues.apache.org/jira/browse/JCR-1066
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: query
>            Reporter: Christoph Kiehl
>            Assignee: Christoph Kiehl
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: patch.txt
>
>
> We already have code that is able to decide whether the system index needs to be included in a search or not (see JCR-967). If I execute a query like "my:app//element(*, my:doc)" this will only search the workspace index. Unfortunately this is slower than "//element(*, my:doc)", since the first query can not be optimized as the second. In our case both queries return the same result set because we use application specific node types. Even though the second query includes the system index it is still faster than the first one. But it could be even faster because it doesn't need to search the system index because nodes with the application specific node type can't be added to the "jcr:system"-tree and are therefore are added never to the system index (am I right?).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.