Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14958
I don't know that the bug that was fixed has manifested yet in Spark;
certainly not in the unit tests. It seems like something that could affect some
execution out in the wild. It seems reasonable to take the fix as I don't see a
downside to it. I don't know if we need to reproduce this same bug; snappy
tests have done that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
