Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/19250
why is this patch so complicated? Based on the fact that data sources
accept a "timezone" option for read/writre, I'd expect it to be just:
* when `CreateTable`, set session local timezone to table property.
* when planning `InsertIntoTable` to concrete data source write command,
get the timezone from table property and put it in write options.
* when plannin table scan to cocrete data source scan, get the timezone
from table property and put it in read options.
For data sources that doesn't support "timezone" options, there is nothing
we can do.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
