Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/21157
Ok it looks like it was @HyukjinKwon who suggested that we remove this hack
in general rather than the partial work around can I get your thoughts on why?
It seems like the partial work around would give us the best of both worlds
(e.g. we don't break peoples existing Spark code and we handle Python tuples
better).
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
