[JCR-1064] Optimize queries that check for the existence of a property

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.4
• Component/s: indexing, jackrabbit-core
• Assignee: Unassigned
• Reporter: Ard Schrijvers
• Created: 15/Aug/07 13:48
• Updated: 15/Jan/08 23:26
• Resolved: 24/Sep/07 08:47

Description

//*[@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

Issue Links

• is blocked by: JCR-1093 Separate initial index creation from MultiIndex construction
• relates to: JCR-1080 Change lucene indexing to a 1:1 mapping for properties instead of current 1:* mapping