SPARK-22371 turns an error to a warning, so it won't break any existing
workloads. Let me backport it to 2.3 so users won't hit this problem in the
new release.
On Fri, May 18, 2018 at 5:59 AM, Imran Rashid wrote:
> I just found
I just found https://issues.apache.org/jira/browse/SPARK-24309 which is
pretty serious. I've marked it a blocker, I think it should go into
2.3.1. I'll also take a closer look comparing to the behavior of the old
listener bus.
On Thu, May 17, 2018 at 12:18 PM, Marcelo Vanzin
Wenchen reviewed and pushed that change, so he's the most qualified to
make that decision.
I plan to cut a new RC tomorrow so hopefully he'll see this by then.
On Thu, May 17, 2018 at 10:13 AM, Artem Rudoy wrote:
> Can we include
Can we include https://issues.apache.org/jira/browse/SPARK-22371 as well
please?
Artem
--
Sent from: http://apache-spark-developers-list.1001551.n3.nabble.com/
-
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
Hi all,
Paul Ogilvie pointed this thread out to me; we overlapped a little at LinkedIn.
It’s good to see that this kind of discussion is going on!
I have some thoughts regarding the discussion going on:
- Practically speaking, one of the lowest hanging fruit is the ability for
Spark to