Allow ComplexPhraseQueryParser to deal with nested ComplexPhraseQuery [LUCENE-8322]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Currently, it is not possible to do special handling (e.g. substituting with or queries) e.g. for wildcard queries in the context of ComplexQueryPhraseParser. The attached patch proposes a small fix to allow nested queries, including a test case.
Patch was authored based on branch_7x
---
Migrated from [LUCENE-8322](https://issues.apache.org/jira/browse/LUCENE-8322) by Otmar Caduff, updated Aug 27 2018
Attachments: [LUCENE-NNNN.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-8322/LUCENE-NNNN.patch)
Contributor guide
Research direction
Start by reviewing the attached LUCENE-NNNN.patch and the existing ComplexPhraseQueryParser test coverage. Trace how nested ComplexPhraseQuery instances are parsed and how wildcard queries are handled in that path. Done means nested queries are accepted and the attached test case passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100