Thank you, Maxim! Dongjoon.
On Thu, May 19, 2022 at 11:49 PM Maxim Gekk <maxim.g...@databricks.com.invalid> wrote: > Hi All, > > The voting for Spark 3.3.0 RC2 has failed since there aren't enough +1 and > due to reported bugs. I will prepare RC3 at the beginning of next week. > > All known issues have been resolved in 3.3 already (at least the issues > reported in the thread). Please, test the current branch-3.3 and report any > issues. > > Maxim Gekk > > Software Engineer > > Databricks, Inc. > > > On Thu, May 19, 2022 at 1:59 PM Emil Ejbyfeldt > <eejbyfe...@liveintent.com.invalid> wrote: > >> Hi, >> >> When testing out Spark 3.3.0 on our production spark workload it was >> noticed that https://issues.apache.org/jira/browse/SPARK-38681 is >> actually a regression from 3.2 (I did not know this a the time of >> creating the ticket) seem like the bug was introduced in >> https://github.com/apache/spark/pull/33205 >> >> I already have a PR here that fixes the issue: >> https://github.com/apache/spark/pull/36004 >> >> Since this is a breaking regression for us I think it might be for other >> people as well. >> >> Best, >> Emil >> >> On 16/05/2022 14:43, Maxim Gekk wrote: >> > Please vote on releasing the following candidate as >> > Apache Spark version 3.3.0. >> > >> > The vote is open until 11:59pm Pacific time May 19th and passes if a >> > majority +1 PMC votes are cast, with a minimum of 3 +1 votes. >> > >> > [ ] +1 Release this package as Apache Spark 3.3.0 >> > [ ] -1 Do not release this package because ... >> > >> > To learn more about Apache Spark, please see http://spark.apache.org/ >> > <http://spark.apache.org/> >> > >> > The tag to be voted on is v3.3.0-rc2 (commit >> > c8c657b922ac8fd8dcf9553113e11a80079db059): >> > https://github.com/apache/spark/tree/v3.3.0-rc2 >> > <https://github.com/apache/spark/tree/v3.3.0-rc2> >> > >> > The release files, including signatures, digests, etc. can be found at: >> > https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc2-bin/ >> > <https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc2-bin/> >> > >> > Signatures used for Spark RCs can be found in this file: >> > https://dist.apache.org/repos/dist/dev/spark/KEYS >> > <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-1403 >> > <https://repository.apache.org/content/repositories/orgapachespark-1403 >> > >> > >> > The documentation corresponding to this release can be found at: >> > https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc2-docs/ >> > <https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc2-docs/> >> > >> > The list of bug fixes going into 3.3.0 can be found at the following >> URL: >> > https://issues.apache.org/jira/projects/SPARK/versions/12350369 >> > <https://issues.apache.org/jira/projects/SPARK/versions/12350369> >> > >> > This release is using the release script of the tag v3.3.0-rc2. >> > >> > >> > 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 a out of date RC going forward). >> > >> > =========================================== >> > What should happen to JIRA tickets still targeting 3.3.0? >> > =========================================== >> > The current list of open tickets targeted at 3.3.0 can be found at: >> > https://issues.apache.org/jira/projects/SPARK >> > <https://issues.apache.org/jira/projects/SPARK> and search for "Target >> > Version/s" = 3.3.0 >> > >> > Committers should look at those and triage. Extremely important bug >> > fixes, documentation, and API tweaks that impact compatibility should >> > be worked on immediately. Everything else please retarget to an >> > appropriate release. >> > >> > ================== >> > But my bug isn't fixed? >> > ================== >> > In order to make timely releases, we will typically not hold the >> > release unless the bug in question is a regression from the previous >> > release. That being said, if there is something which is a regression >> > that has not been correctly targeted please ping me or a committer to >> > help target the issue. >> > >> > Maxim Gekk >> > >> > Software Engineer >> > >> > Databricks, Inc. >> > >> >> --------------------------------------------------------------------- >> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >> >>
