Stop IndexWriter from writing broken term vector offset data in 5.0 [LUCENE-4957]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Today we allow this in (some analyzers are broken), and only reject them if someone is indexing offsets into the postings lists.
But we should ban this also when term vectors are enabled. Its time to stop writing this broken data and let broken analyzers be broken.
---
Migrated from [LUCENE-4957](https://issues.apache.org/jira/browse/LUCENE-4957) by Robert Muir (@rmuir), updated Mar 19 2014
Attachments: [LUCENE-4957.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4957/LUCENE-4957.patch)
Contributor guide
Research direction
Start at IndexWriter and review the migrated LUCENE-4957.patch to trace how term-vector offsets are accepted. Confirm the relevant indexing tests and make sure analyzers producing invalid term-vector offset data are rejected rather than written.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100