Kent Yao bdd3b49026 [SPARK-36552][SQL] Fix different behavior for writing char/varchar to hive and datasource table ... ### What changes were proposed in this pull request? For the hive table, the actual write path and the schema handling are inconsistent when `spark.sql.legacy.charVarcharAsString` is true. This causes problems like SPARK-36552 described. In this PR we respect `spark.sql.legacy.charVarcharAsString` when generates hive table schema from spark data types. ### Why are the changes needed? bugfix ### Does this PR introduce _any_ user-facing change? yes, when `spark.sql.legacy.charVarcharAsString` is true, hive table with char/varchar will respect string behavior. ### How was this patch tested? newly added test Closes #33798 from yaooqinn/SPARK-36552. Authored-by: Kent Yao <yao@apache.org> Signed-off-by: Hyukjin Kwon <gurwls223@apache.org> (cherry picked from commit f918c123a0) Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>		2021-08-22 09:38:54 +09:00
..
main	[SPARK-36552][SQL] Fix different behavior for writing char/varchar to hive and datasource table	2021-08-22 09:38:54 +09:00
test	[SPARK-36552][SQL] Fix different behavior for writing char/varchar to hive and datasource table	2021-08-22 09:38:54 +09:00