[LUCENE-508] SegmentTermEnum.next() doesn't maintain prevBuffer at end

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.9, 2.0.0
• Fix Version/s: 2.3
• Component/s: core/index

Environment

Lucene Trunk

• Assignee: Michael McCandless
• Reporter: Steven Tamm
• Created: 02/Mar/06 12:05
• Updated: 28/Aug/22 11:25
• Resolved: 07/Jan/08 21:16

Description

When you're iterating a SegmentTermEnum and you go past the end of the docs, you end up with a state where the nextBuffer = null and the prevBuffer is the penultimate term, not the last term. This patch fixes it. (It's also required for my Prefetching bug LUCENE-506)

Index: java/org/apache/lucene/index/SegmentTermEnum.java
===================================================================
— java/org/apache/lucene/index/SegmentTermEnum.java (revision 382121)
+++ java/org/apache/lucene/index/SegmentTermEnum.java (working copy)
@@ -109,6 +109,7 @@
/** Increments the enumeration to the next element. True if one exists.*/
public final boolean next() throws IOException {
if (position++ >= size - 1)

{ + prevBuffer.set(termBuffer); termBuffer.reset(); return false; }