Replace payloadprocessorprovider with a codec that overrides merging [LUCENE-3568]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Seems like this would be a much cleaner integration (and ultimately more flexible).
Instead of hardcoding this api into our default termsconsumer, we could just have a postingsformat (wrapper?)
that does special things with payloads during merging.
---
Migrated from [LUCENE-3568](https://issues.apache.org/jira/browse/LUCENE-3568) by Robert Muir (@rmuir)
Contributor guide
Research direction
No files, tests, or concrete entry points are named. Start by reviewing the migrated LUCENE-3568 discussion and the existing payloadprocessorprovider, default termsconsumer, and postingsformat integration. Done should mean payload merging is handled through a codec or postings-format wrapper rather than a hardcoded default-termsconsumer API, with the resulting design validated by relevant tests.
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