jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1066) Exclude system index for queries that restrict the result set to nodetypes not availble in the "jcr:system" subtree
Date Tue, 21 Aug 2007 13:05:30 GMT

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

Marcel Reutegger commented on JCR-1066:
---------------------------------------

There's another potential issue. I know of at least one implementation that customizes jackrabbit
and uses more than the listed node types under /jcr:system. We should try to make the list
customizable.

We could move the list to the SearchIndex class and add a parameter to the method QueryNode.needsSystemTree().
We'd then have: 

public abstract boolean needsSystemTree(Set jcrSystemNodeTypes);

where jcrSystemNodeTypes is a Set of QNames.

> 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.


Mime
View raw message