[SPARK-53077][CORE][TESTS][FOLLOWUP] Reduce insertion count in SparkBloomFilterSuite #51845
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
reduce insertion count in SparkBloomFilterSuite to mitigate long running time
What changes were proposed in this pull request?
This change reduces the insertion count in the
SparkBloomFilterSuite
testsuite to the bare minimum that's necessary to demonstrate the int truncation bug in the V1 version ofBloomFilterImpl
.Why are the changes needed?
#50933 introduced a new
SparkBloomFilterSuite
testsuite which increased the test running time of the common/sketch module from about 7s to a whopping 12minutes. This change is a workaround to decrease the test running time, until we can devise a way to then (and only then) trigger these long running tests when there are actual changes done incommon/sketch
.Does this PR introduce any user-facing change?
No
How was this patch tested?
the minimum insertion count was selected based on the following measurements with the V1 version of the
BloomFilterImpl
:Was this patch authored or co-authored using generative AI tooling?
No