Skip to content

[spark] Align spark.paimon.branch option with explicit branch syntax for chain tables#8016

Merged
JingsongLi merged 1 commit into
apache:masterfrom
juntaozhang:pr-align-with-branch_xxx
Jun 2, 2026
Merged

[spark] Align spark.paimon.branch option with explicit branch syntax for chain tables#8016
JingsongLi merged 1 commit into
apache:masterfrom
juntaozhang:pr-align-with-branch_xxx

Conversation

@juntaozhang
Copy link
Copy Markdown
Contributor

Purpose

#8015

Tests

SparkChainTableITCase.testChainTableWithBranchOption

@leaves12138
Copy link
Copy Markdown
Contributor

Thanks for the fix. I am holding off on approval for now because the current CI status still has a failing build_test job. Please fix or rerun it, then I can take another pass.

@juntaozhang juntaozhang force-pushed the pr-align-with-branch_xxx branch from ff19ac6 to bb2f1e0 Compare May 31, 2026 13:13
@juntaozhang
Copy link
Copy Markdown
Contributor Author

Hi @leaves12138, appreciate your feedback, PTAL.
Thanks

@JingsongLi
Copy link
Copy Markdown
Contributor

Reviewed with focus on alignment between the deprecated spark.paimon.branch option and the explicit Java/Paimon table$branch_xxx identifier path.

Applying the option before catalog.getTable(...) makes the Spark catalog resolve the same branched Identifier that explicit branch syntax would use, while leaving an explicit branch name untouched. I also verified the common Spark module compiles with:

mvn -pl paimon-spark/paimon-spark-common -am -Pfast-build -DskipTests compile

No additional blocker from my side.

@JingsongLi JingsongLi merged commit 4eafdcc into apache:master Jun 2, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants