Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes SplitIT.bulkImportThatCantSplitHangsCompaction #5148

Merged
merged 1 commit into from
Dec 9, 2024

Conversation

keith-turner
Copy link
Contributor

This test was making a incorrect assumption that a table with no splits and data for a single row could not split. What would actually happen is that the table would split once for the single row in the data and then still need to split but be unable to. Added single split at table creation time to fix this.

Before these changes the test would add data to a table and then immediately check that its splits were zero. The table would eventually split, but usually the check in the test would happen prior to this. This race condition in the test hid the flawed assumption in the test. Added a wait to the test to fix this.

This test was making a incorrect assumption that a table with no splits
and data for a single row could not split.  What would actually happen
is that the table would split once for the single row in the data and
then still need to split but be unable to.  Added single split at table
creation time to fix this.

Before these changes the test would add data to a table and then
immediately check that its splits were zero.  The table would eventually
split, but usually the check in the test would happen prior to this.
This race condition in the test hid the flawed assumption in the test.
Added a wait to the test to fix this.
@ddanielr ddanielr merged commit 2d27803 into apache:main Dec 9, 2024
8 checks passed
asfgit pushed a commit that referenced this pull request Dec 16, 2024
* Fix unused import introduced in #5127
* Remove dead code for `--fixFiles` in Admin checks left by #4957
* Fix unclosed resource warning introduced in #5148
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants