I agree it is a non-important Spark bug. I mean the Option and 
String comparison. The bug is easy to fix and obvious to confirm. If the desc 
of PR may not be accurate,feel free to edit the title or content. I am on a 
vocation from 9.29   :)But the scala bug of WrappedArray is severe. We should 
not provide a pre-built spark packages with Scala 2.12.6 . The bug is not about 
compiler. But about scala-library.If the prebuilt packages of Spark use 
scala-library 2.12.6 , the bug exists whatever scala version our application 
developer use.For Spark we should be serious about the minor Scala version. A 
preferred Scala minor version should be officially stated. (hi wenchen sorry 
for the duplication of email ,just forgot to cc the list)---- On Fri, 28 Sep 
2018 22:38:05 +0800  Wenchen Fan<cloud0...@gmail.com> wrote ----I don't think 
this bug is so serious to fail an RC, it's only about metrics IIUC, and it's 
not a regression in 2.4.I agree we should backport this fix to 2.3 and 2.4, and 
we should update our scala 2.12 jenkins build to use scala 2.12.7. cc Shane do 
you know how to change it?BTW end users can still use scala 2.12.7 with the 
Spark package built with scala 2.12.6, right?On Fri, Sep 28, 2018 at 4:22 PM 
Darcy Shen <sad...@zoho.com> wrote:-1 
see:https://github.com/apache/spark/pull/22577We should make sure that Spark 
works with Scala 2.12.7 .https://github.com/scala/bug/issues/11123This resolved 
bug of Scala 2.12.6 is severe and related to correctness.We should warn our 
aggressive users about the Scala version. Latest Scala (2.12.7) is preferred 
and should pass the unit tests at least.---- On Fri, 28 Sep 2018 10:59:41 +0800 
Wenchen Fan <cloud0...@gmail.com> wrote ----Please vote on releasing the 
following candidate as Apache Spark version 2.4.0.The vote is open until 
October 1 PST and passes if a majority +1 PMC votes are cast, witha minimum of 
3 +1 votes.[ ] +1 Release this package as Apache Spark 2.4.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 v2.4.0-rc2 (commit 
42f25f309e91c8cde1814e3720099ac1e64783da):https://github.com/apache/spark/tree/v2.4.0-rc2The
 release files, including signatures, digests, etc. can be found 
at:https://dist.apache.org/repos/dist/dev/spark/v2.4.0-rc2-bin/Signatures used 
for Spark RCs can be found in this 
file:https://dist.apache.org/repos/dist/dev/spark/KEYSThe staging repository 
for this release can be found 
at:https://repository.apache.org/content/repositories/orgapachespark-1287The 
documentation corresponding to this release can be found 
at:https://dist.apache.org/repos/dist/dev/spark/v2.4.0-rc2-docs/The list of bug 
fixes going into 2.4.0 can be found at the following 
URL:https://issues.apache.org/jira/projects/SPARK/versions/2.4.0FAQ=========================How
 can I help test this release?=========================If you are a Spark user, 
you can help us test this release by takingan existing Spark workload and 
running on this release candidate, thenreporting any regressions.If you're 
working in PySpark you can set up a virtual env and installthe current RC and 
see if anything important breaks, in the Java/Scalayou can add the staging 
repository to your projects resolvers and testwith the RC (make sure to clean 
up the artifact cache before/after soyou don't end up building with a out of 
date RC going forward).===========================================What should 
happen to JIRA tickets still targeting 
2.4.0?===========================================The current list of open 
tickets targeted at 2.4.0 can be found 
at:https://issues.apache.org/jira/projects/SPARK and search for "Target 
Version/s" = 2.4.0Committers should look at those and triage. Extremely 
important bugfixes, documentation, and API tweaks that impact compatibility 
shouldbe worked on immediately. Everything else please retarget to 
anappropriate release.==================But my bug isn't 
fixed?==================In order to make timely releases, we will typically not 
hold therelease unless the bug in question is a regression from the 
previousrelease. That being said, if there is something which is a 
regressionthat has not been correctly targeted please ping me or a committer 
tohelp target the issue. 
        
        

    
    

Reply via email to