[OAK-2177] Configurable Analyzer in Lucene index

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.1.6
• Component/s: lucene
• Assignee: Chetan Mehrotra
• Reporter: Tommaso Teofili
• Created: 12/Oct/14 21:19
• Updated: 08/Oct/19 15:22
• Resolved: 20/Jan/15 12:38

Description

Currently the OakAnalyzer is used by default for each Lucene field, sometimes using a different analyzer is needed though.
It should be possible to make that configurable to support things like: multiple languages, stopword filtering, synonyms expansion, stemming, etc.

Issue Links

• is blocked by: OAK-2301 QueryEngine should not tokenize fulltext expression by default
• is required by: OAK-4516 Configurable option to lucene index defs to index original (unanalyzed value as well)

Sub-Tasks

• Export Lucene packages: Closed
• Use LuceneQuery parser to create query from fulltext string: Closed