Many of these changes are not needed - please see how the profiles work.
Please also open 1 PR for one logical change and not 4.
On Fri, Feb 5, 2016, 06:03 zzc <441586...@qq.com> wrote:
> Hi Prashant Sharma, i saw that there already were some pr submitted by
> Luciano Resende:
> https://github.co
Hi Prashant Sharma, i saw that there already were some pr submitted by
Luciano Resende:
https://github.com/apache/spark/pull/11075
https://github.com/apache/spark/pull/11074
https://github.com/apache/spark/pull/11076
https://github.com/apache/spark/pull/11077
--
View this message in context:
ht
There were few more issues, I have started tracking them at
https://issues.apache.org/jira/browse/SPARK-13189
On Thu, Feb 4, 2016 at 2:08 AM, Prashant Sharma
wrote:
> Yes, That should be changed to 2.11.7. Mind sending a patch ?
>
> Prashant Sharma
>
>
>
> On Thu, Feb 4, 2016 at 2:11 PM, zzc <4
Yes, That should be changed to 2.11.7. Mind sending a patch ?
Prashant Sharma
On Thu, Feb 4, 2016 at 2:11 PM, zzc <441586...@qq.com> wrote:
> hi, rxin, in pom.xml file, 'scala.version' still is 2.10.5, does it need
> to
> be modified to 2.11.7?
>
>
>
> --
> View this message in context:
> htt
hi, rxin, in pom.xml file, 'scala.version' still is 2.10.5, does it need to
be modified to 2.11.7?
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/Scala-2-11-default-build-tp16157p16207.html
Sent from the Apache Spark Developers List mailing list arch
Yes they do. We haven't dropped 2.10 support yet. There are too many 2.10
active deployments out there.
On Mon, Feb 1, 2016 at 11:33 AM, Jakob Odersky wrote:
> Awesome!
> +1 on Steve Loughran's question, how does this affect support for
> 2.10? Do future contributions need to work with Scala 2.
Awesome!
+1 on Steve Loughran's question, how does this affect support for
2.10? Do future contributions need to work with Scala 2.10?
cheers
On Mon, Feb 1, 2016 at 7:02 AM, Ted Yu wrote:
> The following jobs have been established for build against Scala 2.10:
>
> https://amplab.cs.berkeley.edu/
The following jobs have been established for build against Scala 2.10:
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/SPARK-master-COMPILE-MAVEN-SCALA-2.10/
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/SPARK-master-COMPILE-sbt-SCALA-2.10/
FYI
On Mon,
On 30 Jan 2016, at 08:22, Reynold Xin
mailto:r...@databricks.com>> wrote:
FYI - I just merged Josh's pull request to switch to Scala 2.11 as the default
build.
https://github.com/apache/spark/pull/10608
does this mean that Spark 2.10 compatibility & testing are no longer needed?
Does this mean the following Jenkins builds can be disabled ?
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/SPARK-master-COMPILE-MAVEN-SCALA-2.11/
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/SPARK-master-COMPILE-sbt-SCALA-2.11/
Cheers
On Sat, Jan 3
Nice, good work!
I've been using a Docker container to compile against 2.11:
https://github.com/fokko/docker-spark
Cheers, Fokko
2016-01-30 9:22 GMT+01:00 Reynold Xin :
> FYI - I just merged Josh's pull request to switch to Scala 2.11 as the
> default build.
>
> https://github.com/apache/spark
FYI - I just merged Josh's pull request to switch to Scala 2.11 as the
default build.
https://github.com/apache/spark/pull/10608
12 matches
Mail list logo