TermsQuery should use AutomatonQuery or Terms.intersect [LUCENE-3893]
Open
legacy-jira-label:gsoc2014
legacy-jira-priority:Major
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
I think we could see perf gains if TermsFilter sorted the terms, built a minimal automaton, and used TermsEnum.intersect to visit the terms...
This idea came up on the dev list recently.
---
Migrated from [LUCENE-3893](https://issues.apache.org/jira/browse/LUCENE-3893) by Michael McCandless (@mikemccand), updated Jun 10 2015
Linked issues:
- #5985
- #5577
Contributor guide
Research direction
Start by reading TermsFilter, TermsQuery, AutomatonQuery, and TermsEnum.intersect to understand the proposed search path. Review linked issues #5985 and #5577 and the referenced developer-list discussion before deciding scope. Done would require an agreed implementation direction and evidence of performance gains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100