Github user juliuszsompolski commented on the issue:
https://github.com/apache/spark/pull/19181
@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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
