Re: Add hot-deploy capability in Spark Shell

I don't. The hot-deploy shouldn't happen while there is a job running. At least in the REPL it won't make much sense. It's a development-only feature to shorten the iterative coding cycle. In production environment, this is not enabled ... though there might be situations where it would be

Re: Add hot-deploy capability in Spark Shell

Thanks for the email. How do you deal with in-memory state that reference the classes? This can happen in both streaming and caching in RDD and temporary view creation in SQL. On Mon, Jun 6, 2016 at 3:40 PM, S. Kai Chen wrote: > Hi, > > We use spark-shell heavily for

Add hot-deploy capability in Spark Shell

Hi, We use spark-shell heavily for ad-hoc data analysis as well as iterative development of the analytics code. A common workflow consists the following steps: 1. Write a small Scala module, assemble the fat jar 2. Start spark-shell with the assembly jar file 3. Try out some ideas in

Re: apologies for flaky BlacklistIntegrationSuite

Thanks for fixing it! On Mon, Jun 6, 2016 at 1:49 PM, Imran Rashid wrote: > Hi all, > > just a heads up, I introduced a flaky test, BlacklistIntegrationSuite, a > week ago or so. I *thought* I had solved the problems, but turns out there > was more flakiness remaining.

Re: Mesos and No transport is loaded for protocol

Hi, How did you package the spark.tgz, and are you running the same code that you packaged when you ran spark submit? And what is your settings for spark look like? Tim > On Jun 6, 2016, at 12:13 PM, thibaut wrote: > > Hi there, > > I an trying to configure

apologies for flaky BlacklistIntegrationSuite

Hi all, just a heads up, I introduced a flaky test, BlacklistIntegrationSuite, a week ago or so. I *thought* I had solved the problems, but turns out there was more flakiness remaining. for now I've just turned the tests off, so if you this has led to failures for you, just re-trigger your

Re: Spark 2.0.0-preview artifacts still not available in Maven

I've been a bit on the fence on this, but I agree that Luciano makes a compelling reason for why we really should publish things to maven central. Sure we slightly increase the risk somebody refers to the preview release too late, but really that is their own fault. And I also I agree with

Mesos and No transport is loaded for protocol

Hi there, I an trying to configure Spark for running on top of Mesos. But every time I send a job, it fails. I can see mesos downloading correctly the spark.tgz but I have this errors at the end : Any idea ? I did not find anything for solving my issue.. Is it my cluster ? Spark ? both ?

Re: Spark 2.0.0-preview artifacts still not available in Maven

On Mon, Jun 6, 2016 at 12:05 PM, Reynold Xin wrote: > The bahir one was a good argument actually. I just clicked the button to > push it into Maven central. > > Thank You !!!

Re: Spark 2.0.0-preview artifacts still not available in Maven

The bahir one was a good argument actually. I just clicked the button to push it into Maven central. On Mon, Jun 6, 2016 at 12:00 PM, Mark Hamstra wrote: > Fine. I don't feel strongly enough about it to continue to argue against > putting the artifacts on Maven

Re: Spark 2.0.0-preview artifacts still not available in Maven

Artifacts can't be removed from Maven in any normal circumstance, but, it's no problem. The argument that people might keep using it goes for any older release. Why would anyone use 1.6.0 when 1.6.1 exists? yet we keep 1.6.0 just for the record and to not break builds. It may be that Foobar

Re: Spark 2.0.0-preview artifacts still not available in Maven

+1 for moving this discussion to a proactive new (alpha/beta) release of Apache Spark 2.0! > On 06 Jun 2016, at 20:25, Ovidiu Cristian Marcu wrote: > > Any chance to start preparing a new alpha/beta release for 2.0 this month or > the preview will be pushed to maven and

Re: Spark 2.0.0-preview artifacts still not available in Maven

On Mon, Jun 6, 2016 at 11:12 AM, Matei Zaharia wrote: > Is there any way to remove artifacts from Maven Central? Maybe that would > help clean these things up long-term, though it would create problems for > users who for some reason decide to rely on these previews. > >

Re: Spark 2.0.0-preview artifacts still not available in Maven

Is there any way to remove artifacts from Maven Central? Maybe that would help clean these things up long-term, though it would create problems for users who for some reason decide to rely on these previews. In any case, if people are *really* concerned about this, we should just put it there. My

Re: Spark 2.0.0-preview artifacts still not available in Maven

On Mon, Jun 6, 2016 at 10:08 AM, Mark Hamstra wrote: > I still don't know where this "severely compromised builds of limited >> usefulness" thing comes from? what's so bad? You didn't veto its >> release, after all. > > > I simply mean that it was released with the

Re: Spark 2.0.0-preview artifacts still not available in Maven

On Mon, Jun 6, 2016 at 9:51 AM, Sean Owen wrote: > I still don't know where this "severely compromised builds of limited > usefulness" thing comes from? what's so bad? You didn't veto its > release, after all. And rightly so: a release doesn't mean "definitely > works"; it

Re: Can't compile 2.0-preview with scala 2.10

See the following from https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/job/SPARK-master-COMPILE-sbt-SCALA-2.10/1642/consoleFull : + SBT_FLAGS+=('-Dscala-2.10') + ./dev/change-scala-version.sh 2.10 FYI On Mon, Jun 6, 2016 at 10:35 AM, Franklyn D'souza <

Can't compile 2.0-preview with scala 2.10

Hi, I've checked out the 2.0-preview and attempted to build it with ./dev/make-distribution.sh -Pscala-2.10 However i keep getting [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ spark-parent_2.11 --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies

Re: Spark 2.0.0-preview artifacts still not available in Maven

> > I still don't know where this "severely compromised builds of limited > usefulness" thing comes from? what's so bad? You didn't veto its > release, after all. I simply mean that it was released with the knowledge that there are still significant bugs in the preview that definitely would

Re: Spark 2.0.0-preview artifacts still not available in Maven

I still don't know where this "severely compromised builds of limited usefulness" thing comes from? what's so bad? You didn't veto its release, after all. And rightly so: a release doesn't mean "definitely works"; it means it was created the right way. It's OK to say it's buggy alpha software;

subscribe

Re: Spark 2.0.0-preview artifacts still not available in Maven

+1 to what Mark said. I've been following this discussion and I don't understand where the sudden "Databricks vs. everybody else" narrative came from. On Mon, Jun 6, 2016 at 11:00 AM Mark Hamstra wrote: > This is not a Databricks vs. The World situation, and the fact

Re: Welcoming Yanbo Liang as a committer

Congratulations Yanbo Liang! Well deserved. On Sun, Jun 5, 2016 at 7:10 PM, Shixiong(Ryan) Zhu wrote: > Congrats, Yanbo! > > On Sun, Jun 5, 2016 at 6:25 PM, Liwei Lin wrote: > >> Congratulations Yanbo! >> >> On Mon, Jun 6, 2016 at 7:07 AM, Bryan

Re: Spark 2.0.0-preview artifacts still not available in Maven

This is not a Databricks vs. The World situation, and the fact that some persist in forcing every issue into that frame is getting annoying. There are good engineering and project-management reasons not to populate the long-term, canonical repository of Maven artifacts with what are known to be

Re: https://issues.apache.org seems to be down for a while today.

Yes, Jira was down couple of hours ago, but it's back now. Regards JB On 06/06/2016 12:51 PM, Prashant Sharma wrote: Hi All, https://issues.apache.org seems to be down for a while today. I was not sure, who looks into this. http://downorisitjustme.com/res.php?url=issues.apache.org Thanks,