[LUCENE-4221] CheckIndex is overeager for term vector offsets bounds checks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0-ALPHA
• Fix Version/s: 4.0-BETA, 6.0
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Robert Muir
• Created: 15/Jul/12 02:31
• Updated: 28/Aug/22 13:22
• Resolved: 03/Aug/12 13:20

Description

In some situations (like running shingles twice), you end out with a case where startOffset > endOffset.

We prevent this in IndexWriter for postings offsets, but we never do any validation here for term vectors (at some point, maybe we should make a plan to address this?)

Anyway, currently CheckIndex will wrongly fail in this situation, which some of our own analyzers even do (e.g. LUCENE-3920)...

This is an overly-eager validation in checkindex (for vectors, we cannot safely do these assertions as it was/is never enforced by IndexWriter, only for postings offsets).

Issue Links

• is related to: LUCENE-4641 Fix analyzer bugs documented in TestRandomChains