It's fixed at https://github.com/apache/spark/pull/36762.
On Fri, Jun 3, 2022 at 2:20 PM Sean Owen <sro...@apache.org> wrote: > > Ah yeah, I think it's this change from 15 hrs ago. That needs to be .toSeq: > > https://github.com/apache/spark/commit/4a0f0ff6c22b85cb0fc1eef842da8dbe4c90543a#diff-01813c3e2e933ed573e4a93750107f004a86e587330cba5e91b5052fa6ade2a5R146 > > On Fri, Jun 3, 2022 at 4:13 PM Sean Owen <sro...@apache.org> wrote: >> >> In Scala 2.13, I'm getting errors like this: >> >> analyzer should replace current_timestamp with literals *** FAILED *** >> java.lang.ClassCastException: class scala.collection.mutable.ArrayBuffer >> cannot be cast to class scala.collection.immutable.Seq >> (scala.collection.mutable.ArrayBuffer and scala.collection.immutable.Seq are >> in unnamed module of loader 'app') >> at >> org.apache.spark.sql.catalyst.optimizer.ComputeCurrentTimeSuite.literals(ComputeCurrentTimeSuite.scala:146) >> ... >> - analyzer should replace current_date with literals *** FAILED *** >> java.lang.ClassCastException: class scala.collection.mutable.ArrayBuffer >> cannot be cast to class scala.collection.immutable.Seq >> (scala.collection.mutable.ArrayBuffer and scala.collection.immutable.Seq are >> in unnamed module of loader 'app') >> ... >> >> I haven't investigated yet, just flagging in case anyone knows more about it >> immediately. >> >> >> On Fri, Jun 3, 2022 at 9:54 AM Maxim Gekk >> <maxim.g...@databricks.com.invalid> wrote: >>> >>> Please vote on releasing the following candidate as Apache Spark version >>> 3.3.0. >>> >>> The vote is open until 11:59pm Pacific time June 7th 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/ >>> >>> The tag to be voted on is v3.3.0-rc4 (commit >>> 4e3599bc11a1cb0ea9fc819e7f752d2228e54baf): >>> https://github.com/apache/spark/tree/v3.3.0-rc4 >>> >>> The release files, including signatures, digests, etc. can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc4-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-1405 >>> >>> The documentation corresponding to this release can be found at: >>> https://dist.apache.org/repos/dist/dev/spark/v3.3.0-rc4-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 >>> >>> This release is using the release script of the tag v3.3.0-rc4. >>> >>> >>> 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 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
