[OAK-2329] Use LuceneQuery parser to create query from fulltext string

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.6
• Component/s: lucene
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 09/Dec/14 13:45
• Updated: 16/Feb/21 09:52
• Resolved: 20/Jan/15 12:37

Description

Currently the Oak QueryEngine parses the fulltext expression and
produces the FulltextExpression. This was required for runtime
aggregation to work. This allowe [d the LuceneIndex to just convert
the given text (in FulltextTerm) to corresponding Lucene Query [1].

Note that JCR contract for fulltext clause [2] supports some grammer
which was so far handled by the Oak QueryEngine.

Now when moving to index time aggregation it was realized that such parsing of fulltext expression is problamatic [3] in presence of
different analyzers. As we fix that we need also support the
requirements mentioned in [2]. JR2 used to do that via Lucene
QueryParser [4].

As a fix LucenePropertyIndex should use a Lucene QueryParser to construct the query.

Now need to determine which parser to use [5] . SimpleQueryParser looks useful!

[1] https://github.com/apache/jackrabbit-oak/blob/trunk/oak-lucene/src/main/java/org/apache/jackrabbit/oak/plugins/index/lucene/LucenePropertyIndex.java#L913
[2] http://www.day.com/specs/jcr/1.0/6.6.5.2_jcr_contains_Function.html
[3] https://issues.apache.org/jira/browse/OAK-2301
[4] https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-core/src/main/java/org/apache/jackrabbit/core/query/lucene/JackrabbitQueryParser.java
[5] https://lucene.apache.org/core/4_7_0/queryparser/

Issue Links

• is related to: OAK-2424 Support wildcard query for text involving symbol which are not alphabets