Github user squito commented on the issue:
https://github.com/apache/spark/pull/16781
@ueshin I've updated this to remove the conf entirely. So updating your
previous description, the new behavior can be described as:
when creating table:
* if a property `PARQUET_TIMEZONE_TABLE_PROPERTY` exists
* include the table property `PARQUET_TIMEZONE_TABLE_PROPERTY`
* use the `PARQUET_TIMEZONE_TABLE_PROPERTY` value
* else
* don't include table property `PARQUET_TIMEZONE_TABLE_PROPERTY`
when writing/reading data:
* if a table property `PARQUET_TIMEZONE_TABLE_PROPERTY` exists
* use the `PARQUET_TIMEZONE_TABLE_PROPERTY` value to adjust timezone
* else
* don't adjust timezone
---
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
