We see a regression since 1.6.2. I think this PR needs to be backported https://github.com/apache/spark/pull/13784 which resolves SPARK-16078. The PR that causes the issue (for SPARK-15613) was reverted just before 1.6.2 release then re-applied afterwards but this fix was only backported to 2.0.
Test failure: org.apache.spark.sql.catalyst.util.DateTimeUtilsSuite.to UTC timestamp On Tue, 18 Oct 2016 at 01:19 Reynold Xin <r...@databricks.com> wrote: > Please vote on releasing the following candidate as Apache Spark version > 1.6.3. The vote is open until Thursday, Oct 20, 2016 at 18:00 PDT and > passes if a majority of at least 3+1 PMC votes are cast. > > [ ] +1 Release this package as Apache Spark 1.6.3 > [ ] -1 Do not release this package because ... > > > The tag to be voted on is v1.6.3-rc1 > (7375bb0c825408ea010dcef31c0759cf94ffe5c2) > > This release candidate addresses 50 JIRA tickets: > https://s.apache.org/spark-1.6.3-jira > > The release files, including signatures, digests, etc. can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-1.6.3-rc1-bin/ > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/pwendell.asc > > The staging repository for this release can be found at: > https://repository.apache.org/content/repositories/orgapachespark-1205/ > > The documentation corresponding to this release can be found at: > http://people.apache.org/~pwendell/spark-releases/spark-1.6.3-rc1-docs/ > > > ======================================= > == 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 from 1.6.2. > > ================================================ > == What justifies a -1 vote for this release? > ================================================ > This is a maintenance release in the 1.6.x series. Bugs already present > in 1.6.2, missing features, or bugs related to new features will not > necessarily block this release. > >
