Github user eyalfa commented on the issue:
https://github.com/apache/spark/pull/19181
I agree, but 'it is what it is'ð
We can probably come up with some mechanism that detects such scenarios and
avoids invoking the spill method on an object whose already 'on the stack',
I think this requires more involvement from the committers, perhaps in a
separate Jira?
On Sep 15, 2017 14:27, "Juliusz Sompolski" <[email protected]> wrote:
> @eyalfa <https://github.com/eyalfa> Thanks. I agree that this is a good
> fix to this issue and lgtm.
> I'm just worried that there are more lurking cases where a nested spill
> can trigger and cause something unexpected, and that finding and
> reproducing such other similar issues may be difficult.
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/spark/pull/19181#issuecomment-329755551>, or
mute
> the thread
>
<https://github.com/notifications/unsubscribe-auth/ABFFOSIoc8O29CLcpfn2hPWJV_5neQjqks5sil8WgaJpZM4PSVvS>
> .
>
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
