I don't see any new features/functions for these blockers. For SPARK-31257 (which is filed and marked as a blocker from me), I agree unifying create table syntax shouldn't be a blocker for Spark 3.0.0, as that is a new feature, but even we put the proposal aside, the problem remains the same and I think it's still a blocker.
We have a discussion thread for SPARK-31257 - let's revive the thread if we wouldn't be able to adopt proposed solution in Spark 3.0.0. https://lists.apache.org/thread.html/rf1acfaaa3de2d3129575199c28e7d529d38f2783e7d3c5be2ac8923d%40%3Cdev.spark.apache.org%3E On Fri, May 8, 2020 at 9:41 AM Xiao Li <lix...@databricks.com> wrote: > Below are the three major blockers. I think we should start discussing how > to unblock the release. > <https://issues.apache.org/jira/browse/SPARK-31257> > > <https://issues.apache.org/jira/browse/SPARK-31257> > - <https://issues.apache.org/jira/browse/SPARK-31257> > https://issues.apache.org/jira/browse/SPARK-31257 > - https://issues.apache.org/jira/browse/SPARK-31399 > - https://issues.apache.org/jira/browse/SPARK-31404 > > In this stage, for the features/functions that are not supported in the > previous releases, we should just simply throw an exception and document it > as a limitation. We do not need to fix all the things to block the release. > Not all of them are blockers. > > Can we start RC2 next week? > > Xiao > > > On Thu, May 7, 2020 at 5:28 PM Sean Owen <sro...@gmail.com> wrote: > >> So, this RC1 doesn't pass of course, but what's the status of RC2 - are >> there outstanding issues? >> >> On Tue, Mar 31, 2020 at 10:04 PM Reynold Xin <r...@databricks.com> wrote: >> >>> Please vote on releasing the following candidate as Apache Spark version >>> 3.0.0. >>> >>> The vote is open until 11:59pm Pacific time Fri Apr 3, 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.0.0 >>> [ ] -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 v3.0.0-rc1 (commit >>> 6550d0d5283efdbbd838f3aeaf0476c7f52a0fb1): >>> https://github.com/apache/spark/tree/v3.0.0-rc1 >>> >>> The release files, including signatures, digests, etc. can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc1-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-1341/ >>> >>> The documentation corresponding to this release can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v3.0.0-rc1-docs/ >>> >>> The list of bug fixes going into 2.4.5 can be found at the following URL: >>> https://issues.apache.org/jira/projects/SPARK/versions/12339177 >>> >>> This release is using the release script of the tag v3.0.0-rc1. >>> >>> >>> 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.0.0? >>> =========================================== >>> The current list of open tickets targeted at 3.0.0 can be found at: >>> https://issues.apache.org/jira/projects/SPARK and search for "Target >>> Version/s" = 3.0.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. >>> >>> >>> Note: I fully expect this RC to fail. >>> >>> >>> >>> > > -- > <https://databricks.com/sparkaisummit/north-america> >
