clean up postingsreader [LUCENE-5808]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
The current postingsreader is \~ 1500 lines of code (mostly duplicated) calling something like 4,000 lines of generated decompression code.
This is really heavyweight and complicated, and bloats the lucene jar. It would be nice to simplify it so we can eventually remove the baggage.
---
Migrated from [LUCENE-5808](https://issues.apache.org/jira/browse/LUCENE-5808) by Robert Muir (@rmuir), updated Jul 10 2014
Attachments: [LUCENE-5808.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-5808/LUCENE-5808.patch)
Contributor guide
Research direction
Start by reading the current postingsreader implementation and the attached LUCENE-5808.patch. Trace how it calls the generated decompression code and identify the duplicated portions before choosing a simplification approach. Done means the postings reader is less heavyweight and the generated-code baggage is reduced without losing its behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100