Speed up SortingMergePolicy by string [LUCENE-6167]
Open
legacy-jira-priority:Major
type:enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Building the sorted docmaps can take a nontrivial amount of time, for String we currently don't do a very good job.
---
Migrated from [LUCENE-6167](https://issues.apache.org/jira/browse/LUCENE-6167) by Robert Muir (@rmuir), updated Jan 09 2015
Attachments: [LUCENE-6167.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-6167/LUCENE-6167.patch)
Contributor guide
Research direction
Start by reading the SortingMergePolicy implementation and the attached LUCENE-6167.patch, focusing on how sorted docmaps are built for String. Compare the relevant path with the existing behavior and confirm that the String case completes faster without changing sorting results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance, search
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100