[WAYANG-768] Fix test initialization in JdbcJoinOperatorTest#769
Merged
Conversation
zkaoudi
approved these changes
Jun 11, 2026
Contributor
|
Thank you for your PR @iwami4438 |
Contributor
|
This closes #769 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Title: [WAYANG-768] Fix test initialization in JdbcJoinOperatorTest
Description:
This PR fixes the intermittent test failures in JdbcJoinOperatorTest caused by table name collisions.(this: #768)
Changes:
Updated test setup to use
@BeforeEachfor cleaner lifecycle management.Added explicit
initDBcalls to ensure database schema is fresh before running tests.Testing:
The changes were verified by running the full test suite with Maven.
run:
./mvnw clean testAll tests passed successfully (log output attached below).