Repository navigation
Conversation
Paimon 1.4.2 has no Spark 4.1 build, so the Spark 4.1 profile depended on the Spark 4.0 artifact and kept the Paimon tests excluded. Paimon 2.1.0 ships paimon-spark-4.1_2.13, so the suite can run there now. The Spark 4.0 profile stays on 1.4.2: the Spark 4.0 build of Paimon 2.x references the Spark 4.1-only Table.constraints() API.
Member
Author
|
Merge Summary:
Posted by |
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
1 participant
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.
Why are the changes needed?
Paimon 1.4.2 has no Spark 4.1 build, so the Spark 4.1 profile had to depend on the Spark 4.0 artifact (
paimon-spark-4.0_2.13) and keepPaimonTestexcluded. Paimon 2.1.0 shipspaimon-spark-4.1_2.13, which unblocks running the Paimon authz suite on Spark 4.1.paimon.version1.4.2 -> 2.1.0 andpaimon.artifact->paimon-spark-${spark.binary.version}_${scala.binary.version}for the Spark 4.1/4.2/4.3 profilesorg.apache.kyuubi.tags.PaimonTestfrommaven.plugin.scalatest.exclude.tagsPaimonTeststays excluded; both profiles aliasspark.binary.versionto 4.1, so they keep resolvingpaimon-spark-4.1_2.13org.apache.spark.sql.connector.catalog.constraints.Constraint(Table.constraints()), so it cannot run on Spark 4.0How was this patch tested?
PaimonCatalogRangerSparkExtensionSuite, Java 17 and Scala 2.13:NoClassDefFoundError: org.apache.spark.sql.connector.catalog.constraints.Constraint, raised inside the authz reflection helper - hence the Spark 4.0 profile stays on 1.4.2HiveCatalogRangerSparkExtensionSuiteon Spark 4.1.2 + Paimon 2.1.0: 53/53 passed.Was this patch assisted by generative AI tooling?
Assisted-by: Codex with gemini-4-argon