CoveringQuery to use multi-valued field length as minimum match [LUCENE-8613]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Currently CoveringQuery uses a long field's value for the minimumMatch for each document.
There are use cases where this value may be derived from the length of a multi-valued field (including docValues).
This request is to support an alternative constructor and implementation for CoveringQuery to take a field name that can be used for the per-document minimum match value.
---
Migrated from [LUCENE-8613](https://issues.apache.org/jira/browse/LUCENE-8613) by Tristan Stevens
Contributor guide
Research direction
Start by locating CoveringQuery and its existing constructors and implementation. Read the current tests for CoveringQuery, if present, to understand how per-document minimumMatch is verified. Done means an alternative field-based path supports multi-valued fields, including docValues, while preserving the existing long-value behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100