Hi,
It seems that the current master is broken twice. I've just sent a PR
for the first one. Please review and merge.
https://github.com/apache/spark/pull/14315
Pozdrawiam,
Jacek Laskowski
https://medium.com/@jaceklaskowski/
Mastering Apache Spark http://bit.ly/mastering-apache-spark
Follow
Gotcha, that'd be great!
On Thu, Jul 21, 2016 at 8:52 PM, Josh Rosen
wrote:
> Yeah, it's on purpose: we had to disable it back when both the master and
> branch-2.0 branches had the same versions in their POMs because that was
> causing the master snapshots to overwrite the 2.0.0-SNAPSHOTS which
Yeah, it's on purpose: we had to disable it back when both the master and
branch-2.0 branches had the same versions in their POMs because that was
causing the master snapshots to overwrite the 2.0.0-SNAPSHOTS which are
generated off of branch-2.0.
I can go ahead and re-enable it later today.
On T
I’m trying to use a Snapshot build off of master, and after looking through
Jenkins it appears that the last commit where the snapshot was built is
back on 757dc2c09d23400dacac22e51f52062bbe471136, 22 days ago:
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Packaging/job/spark-master-maven-sna
+1 (non binding)
Tested PySpark Core, DataFrame/SQL, MLlib and Streaming on a standalone
cluster
On 21 July 2016 at 05:24, Reynold Xin wrote:
> +1
>
>
> On Wednesday, July 20, 2016, Krishna Sankar wrote:
>
>> +1 (non-binding, of course)
>>
>> 1. Compiled OS X 10.11.5 (El Capitan) OK Total time
Title: Message Title
Anonymous stopped wor
