Github user susanxhuynh commented on the issue:
https://github.com/apache/spark/pull/20641
Thanks for the PR! It seems that the previous attempt to fix this
(SPARK-18114) was wrong -- I'm not sure why we didn't catch the problem before,
maybe lack of testing? @krcz My suggestion for this patch is to add a test, in
order to prevent another regression in the future. I've written a unit test for
this -- you could do something similar:
https://github.com/mesosphere/spark/commit/4812ba3d10264f6d22ec654fa16b5810d70c27a9
I will also do more testing with my own integration tests. cc @skonto
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
