[spark] Skip time-travel self-merge test on Spark 3.2 - #9502
Merged
JingsongLi merged 1 commit intoSep 1, 2026
Conversation
Contributor
|
+1 |
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
2 participants
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.
Purpose
The time-travel self-merge test uses relation time-travel syntax (
VERSION AS OF) that Spark 3.2 cannot parse. Spark added this SQL syntax in 3.3, so the new shared test currently fails the Spark 3.2 CI matrix before exercising Paimon behavior.Guard the test with the existing
gteqSpark3_3capability helper. The assumption runs before table creation, and Spark 3.3+ continues to execute the full test.Tests
RowTrackingTest: 47 passed, 2 canceled, 0 failed.RowTrackingTest: 47 passed, 2 canceled, 0 failed.RowTrackingTest: 49 passed, 0 canceled, 0 failed; the guarded time-travel test executed.