Github user zivanfi commented on the issue:
https://github.com/apache/spark/pull/19250
Yes, you understand correctly, the table property affects both the read
path and the write path, while the current workaround used by Hive and Impala
only affects the read path. (Both are Parquet-specific though, I think you
meant to write "writer-specific" when referring to the latter.)
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
