I just noticed JoshRosen sent a PR to this bug.
From: Miao Wang/San Francisco/IBM@IBMUS
To: tomerk11
Cc: dev@spark.apache.org
Date: 09/02/2016 04:04 PM
Subject:Re: critical bugs to be fixed in Spark 2.0.1?
I am trying to reproduce it on my cluster based on your
I am trying to reproduce it on my cluster based on your instructions.
From: tomerk11
To: dev@spark.apache.org
Date: 09/02/2016 12:32 PM
Subject:Re: critical bugs to be fixed in Spark 2.0.1?
We are regularly hitting the issue described in SPARK-17110
(https
We are regularly hitting the issue described in SPARK-17110
(https://issues.apache.org/jira/browse/SPARK-17110) and this is blocking us
from upgrading from 1.6 to 2.0.0.
It would be great if this could be fixed for 2.0.1
--
View this message in context:
http://apache-spark-developers-list.100
would be nice
>
>
>
> Robert
>
>
>
> *From: *Reynold Xin
> *Date: *Monday, August 22, 2016 at 8:14 PM
> *To: *"dev@spark.apache.org"
> *Subject: *critical bugs to be fixed in Spark 2.0.1?
>
>
>
> We should work on a 2.0.1 release soon, since we hav
SPARK-16991 (https://github.com/apache/spark/pull/14661) would be nice
Robert
From: Reynold Xin
Date: Monday, August 22, 2016 at 8:14 PM
To: "dev@spark.apache.org"
Subject: critical bugs to be fixed in Spark 2.0.1?
We should work on a 2.0.1 release soon, since we have fo
We should work on a 2.0.1 release soon, since we have found couple critical
bugs in 2.0.0. Are there any critical bugs outstanding that we should
address in 2.0.1?