SpanMTQWrapper forces public visibility of many internal MTQ classes [LUCENE-4014]
Open
affects-version:4.0-ALPHA
legacy-jira-priority:Major
type:task
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Maybe we should just move this thing to .search and reduce the visibility of a ton
of these internal classes? It doesn't use any sneaky things in the spans api...
just forms a SpanOrQuery.
---
Migrated from [LUCENE-4014](https://issues.apache.org/jira/browse/LUCENE-4014) by Robert Muir (@rmuir)
Contributor guide
Research direction
Start by locating SpanMTQWrapper and its use of the spans API, especially where it forms a SpanOrQuery. Check whether moving it to .search permits reducing the visibility of the referenced MTQ classes; done means the wrapper still works without exposing those internals.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100