[ https://issues.apache.org/jira/browse/JCR-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529473 ]
Ard Schrijvers commented on JCR-1064: ------------------------------------- I didn't look well enough (only checked JCR-1064-2.patch and not the JCR-1064-3.patch ) I'll do the tests this weekend, because I am just about to grab a nice cold beer (and can't think straight anymore this late ) :-) I'll let you know how the tests went, Cheers > 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 > > > //[EMAIL PROTECTED] 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.