Skip to content

Fix wrong BitSet result in MemoryAccountingBitsetCollector#15656

Open
gaobinlong wants to merge 4 commits intoapache:mainfrom
gaobinlong:fix_bitsetcollector
Open

Fix wrong BitSet result in MemoryAccountingBitsetCollector#15656
gaobinlong wants to merge 4 commits intoapache:mainfrom
gaobinlong:fix_bitsetcollector

Conversation

@gaobinlong
Copy link
Contributor

Description

Fixes #15655, add a test method to verify the BitSet result.

Signed-off-by: Binlong Gao <gbinlong@amazon.com>
Signed-off-by: Binlong Gao <gbinlong@amazon.com>
@github-actions github-actions bot added this to the 10.4.0 milestone Feb 2, 2026
Copy link
Contributor

@romseygeek romseygeek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

return ScoreMode.COMPLETE_NO_SCORES;
}

public FixedBitSet getBitSet() {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be package-private instead? Seems like it's only used for testing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to expose a public method for the upstream caller to get the collected result, but at second thought, this can be implemented in a collector manager for this collector, so we don't need to add a public method here, and the bitSet variable is protected, so we can access it directly in the test method. Thanks!

Signed-off-by: Binlong Gao <gbinlong@amazon.com>
Signed-off-by: Binlong Gao <gbinlong@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DocBase not set when switch to next LeafReader causing wrong bitset in MemoryAccountingBitsetCollector

3 participants