Re: Scala 2.10 Merge

2013-12-17 Thread Henry Saputra
W00t :) On Thursday, December 12, 2013, Patrick Wendell wrote: > Hi Developers, > > In the next few days we are planning to merge Scala 2.10 support into > Spark. For those that haven't been following this, Prashant Sharma has been > maintaining the scala-2.10 branch of Spark for several months.

Re: Re : Scala 2.10 Merge

2013-12-16 Thread Evan Chan
ode related to hadoop will also be built in separate > >>> modules for loading on demand? This sounds to me involve a lot of > works. And > >>> you still need to have shim layer and separate code for different > version > >>> API and depends on differen

Re : Scala 2.10 Merge

2013-12-14 Thread andy.petre...@gmail.com
works. And >>> you still need to have shim layer and separate code for different version >>> API and depends on different version Akka etc. Sounds like and even strict >>> demands versus our current approaching on master, and with dynamic class >>> loader in addi

Re: Scala 2.10 Merge

2013-12-14 Thread Sam Bessalah
roaching on master, and with dynamic class >>> loader in addition, And the problem we are facing now are still there? >>> >>> Best Regards, >>> Raymond Liu >>> >>> -Original Message- >>> From: Patrick Wendell [mailto:pwend..

Re: Scala 2.10 Merge

2013-12-14 Thread Nick Pentreath
oaching on master, and with dynamic class >>> loader in addition, And the problem we are facing now are still there? >>> >>> Best Regards, >>> Raymond Liu >>> >>> -Original Message- >>> From: Patrick Wendell [mailto:pwend...@g

Re: Scala 2.10 Merge

2013-12-14 Thread Patrick Wendell
ersus our current approaching on master, and with dynamic class >> loader in addition, And the problem we are facing now are still there? >> >> Best Regards, >> Raymond Liu >> >> -Original Message- >> From: Patrick Wendell [mailto:pwend...@gmail.com] >> Se

Re: Scala 2.10 Merge

2013-12-12 Thread Patrick Wendell
m: Patrick Wendell [mailto:pwend...@gmail.com] > Sent: Thursday, December 12, 2013 5:13 PM > To: dev@spark.incubator.apache.org > Subject: Re: Scala 2.10 Merge > > Also - the code is still there because of a recent merge that took in some > newer changes... we'll be re

RE: Scala 2.10 Merge

2013-12-12 Thread Liu, Raymond
5:13 PM To: dev@spark.incubator.apache.org Subject: Re: Scala 2.10 Merge Also - the code is still there because of a recent merge that took in some newer changes... we'll be removing it for the final merge. On Thu, Dec 12, 2013 at 1:12 AM, Patrick Wendell wrote: > Hey Raymond, > &

Re: Scala 2.10 Merge

2013-12-12 Thread Prashant Sharma
Hey Raymond, I just gave what you said a try but have no intentions of maintaining it. You might want it helpful https://github.com/ScrapCodes/incubator-spark/tree/yarn-2.2 incase you are willing to maintain it. For the record, above branch is updated to master with scala 2.10 and uses akka 2.3-M

Re: Scala 2.10 Merge

2013-12-12 Thread Patrick Wendell
Also - the code is still there because of a recent merge that took in some newer changes... we'll be removing it for the final merge. On Thu, Dec 12, 2013 at 1:12 AM, Patrick Wendell wrote: > Hey Raymond, > > This won't work because AFAIK akka 2.3-M1 is not binary compatible with > akka 2.2.3 (

Re: Scala 2.10 Merge

2013-12-12 Thread Patrick Wendell
Hey Raymond, This won't work because AFAIK akka 2.3-M1 is not binary compatible with akka 2.2.3 (right?). For all of the non-yarn 2.2 versions we need to still use the older protobuf library, so we'd need to support both. I'd also be concerned about having a reference to a non-released version of

RE: Scala 2.10 Merge

2013-12-12 Thread Liu, Raymond
Hi Patrick What does that means for drop YARN 2.2? seems codes are still there. You mean if build upon 2.2 it will break, and won't and work right? Since the home made akka build on scala 2.10 are not there. While, if for this case, can we just use akka 2.3-M1 which run on protobuf 2.5