[spark] Disable v2 write in v1 append location unit tests #6329
Conversation
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
kerwin-zk
force-pushed
the
optimize-ut
branch
2 times, most recently
from
f5a9f7c to
29c7039
Compare
Zouxxyy
reviewed
Sep 25, 2025
| .foreachBatch { | ||
| (batch: Dataset[Row], _: Long) => | ||
| batch.write.format("paimon").mode("append").save(location) | ||
| withSparkSQLConf(("spark.paimon.write.use-v2-write", "false")) { |
There was a problem hiding this comment.
When V2 write is enabled by default, it should bypass V2 write instead of throwing an exception in scenarios that do not support it.
kerwin-zk
force-pushed
the
optimize-ut
branch
from
2f350c9 to
6ab2d07
Compare
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
Disable v2 write in v1 append location unit tests
The operation
batch.write.format("paimon").mode("append").save(location)throws an exception when v2 write is enabled. Therefore, it is necessary to explicitly disable v2 write in the relevant unit tests.Tests
CI