[FLINK-25674] Add drop tables to be idempotent in case of retrials and the related test #18429
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.
This is to avoid the flakiness of the
CassandraConnectorITCase#test*Pojo*
tests due to retrials that try to recreate an already created (and potentially populated) table. This is the quick version that still uses Junit4 andRetryRule
to quickly fix the Cassandra flakiness issue. The version that usesRetryExtension
needs a migration of cassandra tests to junit5 and some parent tests are in flink-streaming and mutualized so it would be done in a next PR.I also added a commit to replace all string literals by constants to avoid existing copy/paste.
R: @tillrohrmann
CC: @zentol