Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/22138
see e.g. https://github.com/apache/spark/pull/20767 for background
Even if this patch doesn't change behavior, if it doesn't really solve the
problem, it may make it harder to solve it correctly.
On Mon, Aug 20, 2018 at 10:32 AM, Jungtaek Lim <notificati...@github.com>
wrote:
> If my understanding is right, looks like current approach has same
> limitation. I guess you're busy, but could you refer some issue number or
> point out some code lines which was based on the reason if you remember
> any? It should help to determine whether this patch breaks more spots or
> not.
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/22138#issuecomment-414336510>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/AAGAB52zi78tff9E-kvPzeB7k0ZnOyFBks5uSsh0gaJpZM4WCUJs>
> .
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
