The error you are seeing is caused by https://issues.apache.org/jira/browse/SPARK-28775.On Mon, Aug 19, 2019 at 10:40 PM Sean Owen <firstname.lastname@example.org> wrote:Things are looking pretty good so far, but a few notes:
I thought we might need this PR to make the 2.12 build of 2.4.x not
try to build Kafka 0.8 support, but, I'm not seeing that 2.4.x + 2.12
builds or tests it?
I can merge this to 2.4 shortly anyway, but not clear it affects the RC.
I'm getting one weird failure in tests:
- daysToMillis and millisToDays *** FAILED ***
8634 did not equal 8633 Round trip of 8633 did not work in tz
for some context and
for a fix for a similar type of issue.
This may be quite specific to a particular version of Java 8, but I'm
testing on the latest (1.8.0_222). We can 'patch' it by allowing for
multiple correct answers here.
It may not hold up the RC unless others see the failure, but I can
work on that anyway.
On Mon, Aug 19, 2019 at 11:55 AM Dongjoon Hyun <email@example.com> wrote:
> Please vote on releasing the following candidate as Apache Spark version 2.4.4.
> The vote is open until August 22nd 10AM 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 2.4.4
> [ ] -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 v2.4.4-rc1 (commit 13f2465c6c8328e988f7215ee5f5d2c5e69e8d21):
> The release files, including signatures, digests, etc. can be found at:
> Signatures used for Spark RCs can be found in this file:
> The staging repository for this release can be found at:
> The documentation corresponding to this release can be found at:
> The list of bug fixes going into 2.4.4 can be found at the following URL:
> This release is using the release script of the tag v2.4.4-rc1.
> 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 2.4.4?
> The current list of open tickets targeted at 2.4.4 can be found at:
> https://issues.apache.org/jira/projects/SPARK and search for "Target Version/s" = 2.4.4
> 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.
To unsubscribe e-mail: firstname.lastname@example.org