jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ard Schrijvers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1064) Optimize queries that check for the existence of a property
Date Fri, 21 Sep 2007 15:15:50 GMT

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

Ard Schrijvers commented on JCR-1064:

> Sorry for not getting back to you sooner. I was distracted with other work lately. 

np, I was pretty occupied as well, but regarding the release plans for 1.4 i thought it might
be worthy to solve it. 

> Based on your work I've created a slightly different patch, which separates the physical
index format version from the index format version that is used > for a query. This means
a MultiIndex has an index format version (decides how nodes are indexed, independent of a
parent query handler) and also > the SearchIndex has an index format version (decides how
a query is executed, also takes a parent query handler into account). 

I think I do understand what you mean, but do you happen to have the patch available (or do
you commit it directly)? I can do some testing if you want to see if it works out in all possible
situations (index from scratch / existing indexes / existing indexes and remove a workspace
index without parent, etc etc)? 

Regards Ard

> Optimize queries that check for the existence of a property
> -----------------------------------------------------------
>                 Key: JCR-1064
>                 URL: https://issues.apache.org/jira/browse/JCR-1064
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: indexing
>    Affects Versions: 1.3.1
>            Reporter: Ard Schrijvers
>            Priority: Minor
>             Fix For: 1.4
>         Attachments: JCR-1064-2.patch, JCR-1064-2.patch, JCR-1064-2.patch, JCR-1064-2.patch,
JCR-1064-3.patch, JCR-1064-DEPR.patch
> //*[@mytext] is transformed into the org.apache.jackrabbit.core.query.lucene.MatchAllQuery,
that through the MatchAllWeight uses the MatchAllScorer.  The calculateDocFilter() in MatchAllScorer
 does not scale and becomes slow for growing number of nodes. 
> Solution: lucene documents will get a new Field:
> public static final String PROPERTIES_SET = "_:PROPERTIES_SET".intern();
> that holds the available properties of this document. 
> NOTE: Lucene indices build without this performance improvement should still work and
fall back to the original implementation

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

View raw message