Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21427
For configuration, I wasn't sure if we should send the whole configuration
map into worker.py side, if we should fix the command writing way, and also was
thinking of the current timezone way is kind of one time thing. Was just
wondering if we really should do that. I am okay if that's the only way and I
should add a configuration for 2.4. Just for clarification, we should probably
remove this configuration in 3.0.0 too.
For the current approach, I thought we better check if there are other
cases possibly broken and see if that makes sense rather then just blocking
this only because there are a bit of behaviour changes.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
