[FLINK-30640][SqlClient] Fix unstable ctas test in CliClientITCase - #21892
Merged
Conversation
Collaborator
lsyldliu
added a commit
to lsyldliu/flink
that referenced
this pull request
Feb 9, 2023
…pache#21892) (cherry picked from commit 550697a)
fsk119
pushed a commit
that referenced
this pull request
Feb 9, 2023
akkinenivijay
pushed a commit
to krisnaru/flink
that referenced
this pull request
Feb 11, 2023
lsyldliu
added a commit
to lsyldliu/flink
that referenced
this pull request
Feb 13, 2023
…pache#21892) (cherry picked from commit 550697a)
mohsenrezaeithe
pushed a commit
to mohsenrezaeithe/flink
that referenced
this pull request
Feb 21, 2023
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.
What is the purpose of the change
Fix the unstable ctas test in CliClientITCase, we should wait for the insert query to finish first, then query the table
Verifying this change
This change is already covered by existing tests.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (no)Documentation