[LUCENE-2216] OpenBitSet#hashCode() may return false for identical sets.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.9, 2.9.1, 3.0
• Fix Version/s: 2.9.4, 3.0.3
• Component/s: core/other
• Lucene Fields: New, Patch Available
• Assignee: Unassigned
• Reporter: Dawid Weiss
• Created: 16/Jan/10 12:20
• Updated: 28/Aug/22 12:18
• Resolved: 23/Nov/10 13:21

Description

OpenBitSet uses an internal buffer of long variables to store set bits and an additional 'wlen' index that points
to the highest used component inside

{@link #bits}

buffer.

Unlike in JDK, the wlen field is not continuously maintained (on clearing bits, for example). This leads to a situation when wlen may point
far beyond the last set bit.

The hashCode implementation iterates over all long components of the bits buffer, rotating the hash even for empty components. This is against the contract of hashCode-equals. The following test case illustrates this:

// initialize two bitsets with different capacity (bits length).
BitSet bs1 = new BitSet(200);
BitSet bs2 = new BitSet(64);
// set the same bit.
bs1.set(3);
bs2.set(3);
        
// equals returns true (passes).
assertEquals(bs1, bs2);
// hashCode returns false (against contract).
assertEquals(bs1.hashCode(), bs2.hashCode());

Fix and test case attached.