-1 I think we should include this bug fix https://github.com/apache/spark/commit/6cd1ccc56321dfa52672cd25f4cfdf2bbc86b3ea. The bug can lead to the unrecoverable job failure.
Thanks, Yi On Tue, May 28, 2024 at 3:45 PM Wenchen Fan <cloud0...@gmail.com> wrote: > Please vote on releasing the following candidate as Apache Spark version > 4.0.0-preview1. > > The vote is open until May 31 PST and passes if a majority +1 PMC votes > are cast, with > a minimum of 3 +1 votes. > > [ ] +1 Release this package as Apache Spark 4.0.0-preview1 > [ ] -1 Do not release this package because ... > > To learn more about Apache Spark, please see http://spark.apache.org/ > > The tag to be voted on is v4.0.0-preview1-rc2 (commit > 7cfe5a6e44e8d7079ae29ad3e2cee7231cd3dc66): > https://github.com/apache/spark/tree/v4.0.0-preview1-rc2 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/spark/v4.0.0-preview1-rc2-bin/ > > Signatures used for Spark RCs can be found in this file: > https://dist.apache.org/repos/dist/dev/spark/KEYS > > The staging repository for this release can be found at: > https://repository.apache.org/content/repositories/orgapachespark-1455/ > > The documentation corresponding to this release can be found at: > https://dist.apache.org/repos/dist/dev/spark/v4.0.0-preview1-rc2-docs/ > > The list of bug fixes going into 4.0.0 can be found at the following URL: > https://issues.apache.org/jira/projects/SPARK/versions/12353359 > > FAQ > > ========================= > How can I help test this release? > ========================= > > If you are a Spark user, you can help us test this release by taking > an existing Spark workload and running on this release candidate, then > reporting any regressions. > > If you're working in PySpark you can set up a virtual env and install > the current RC and see if anything important breaks, in the Java/Scala > you can add the staging repository to your projects resolvers and test > with the RC (make sure to clean up the artifact cache before/after so > you don't end up building with an out of date RC going forward). >
