-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[spark] Fail fast on incompatible query schema in v2 write #8456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kerwin-zk
wants to merge
1
commit into
apache:master
Choose a base branch
from
kerwin-zk:fix-v2-write-schema-validation
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+104
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not catch the PR's own type-mismatch case. On this branch, running
mvn -pl paimon-spark/paimon-spark-ut -am -Pfast-build -DfailIfNoTests=false -DwildcardSuites=org.apache.paimon.spark.sql.PaimonV2WriteSchemaValidationTest -Dtest=none teststill fails at
PaimonOptionTest.scala:331: the insert reachesPaimonV2DataWriterand aborts the Spark job with aSparkExceptioncaused byNegativeArraySizeException, instead of failing here with the newPaimonSparkSessionExtensionsvalidation message. That meansdataSchemais not a reliable proxy for the physical query rows in this write path (or the validation is happening at the wrong layer), so the original fail-fast/corruption path remains unfixed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for checking! I believe that run picked up a stale
paimon-spark-common_2.12-1.5-SNAPSHOTfrom the local repository instead of the one from this branch, so the PR's change was never on the classpath.-Pfast-buildexplicitly activates a profile, which disables theactiveByDefaultactivation of thespark3profile (standard Maven behavior). Withoutspark3, thepaimon-spark-commonmodules drop out of the reactor — the reactor summary of that exact command only contains:so
-amnever compiles this PR's change toPaimonV2WriteBuilder, and the test runs against whatever1.5-SNAPSHOTis installed in~/.m2. If that snapshot predates this PR, the test fails with exactly the signature you saw — I actually produced the same message on purpose while developing (ran the new test against a build with the fix stashed to verify it was red first):Adding the spark3 profile brings the common modules back into the reactor:
and the suite passes (your exact command also passes once the branch's
paimon-spark-commonis installed to the local repo; the PR CI, which builds from scratch, is green on both 2.12 and 2.13 as well):On the layering question: for this insert path
LogicalWriteInfo.schema()is the analyzed query's output schema, which is exactly the row layout the writer receives, so validating it against the table row type inbuild()catches the mismatch on the driver before any task runs. Row-level operations (copyOnWriteScan) andwrite.merge-schemawrites are exempted since their schemas intentionally diverge and are validated elsewhere.