apache / apache/lucene

optimize DocTermOrds in cases where the underlying TermEnum being wraped supports ord() [LUCENE-6545]

Open
#7,603 1 comment 0 reactions 0 assignees View on GitHub
legacy-jira-priority:Major type:enhancement
Dominant language
Java
Stars
3.6k
Forks
1.4k
Avg merge
2d 11h
Merged PRs (30d)
88

Description

Prior to #7587, DocTermOrds had an optimization when the TermEnum of the field being Uninverted already supported ord().

This optimization was removed in #7587 (see r1684704) because it was found to produce incorrect results for numeric fields that had a precisionStep.

This issue is to track the possibility of re-adding a correct version of this optimization.

---
Migrated from [LUCENE-6545](https://issues.apache.org/jira/browse/LUCENE-6545) by Chris M. Hostetter (@hossman), 1 vote
Linked issues:
- #7587

Contributor guide

Open the contributing guide

Research direction

Start by reviewing linked issue #7587 and change r1684704 to understand why the DocTermOrds optimization was removed and how TermEnum.ord() interacts with numeric fields using a precisionStep. Done means a corrected optimization can be evaluated without reproducing the incorrect results that prompted its removal.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.