dchristle edited a comment on pull request #32826: URL: https://github.com/apache/spark/pull/32826#issuecomment-860104224
> Here, I'm saying that what we need for Apache Spark. What we need is the actual verification by testing, not a hunch. Both of us don't want to break Apache Spark 3.2.0, do we? I think there is a misunderstanding. My proposal is to backport `zstd-jni 1.5.0-1` into Kafka/Avro/Parquet so that upcoming minor releases of those projects pick up the change before we put it into Spark. I used the word "hunch" only to indicate that I expect the backporting process in those projects to include `1.5.0` to go smoothly -- based on some of the CI passing -- and not to suggest that we should not test this change to Spark. If getting the change into upcoming dependency minor releases (1.10.x Avro, 2.8.x Kafka, 1.12.x or 1.13.x Parquet) truly does work with no issues, we can synchronize all dependencies in Spark's `pom` in this PR (and convert it to a WIP in the meantime) so we use `1.5.0-1` uniformly where possible before merging to Spark `master` branch for QA testing. What do you think about this plan? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
