Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/22343
Hi, @seancxmao . Should we be consistent? IIRC, all the previous PR raises
Exception to prevent any potential issues. In this case, I have a feeling that
`convertMetastoreXXX` should be used to prevent the problem of Hive behavior by
raising Exception, not hiding the problem of Hive behavior.
> In case-insensitive mode, when converting hive parquet table to parquet
data source, we switch the duplicated fields resolution mode to ask parquet
data source to pick the first matched field - the same behavior as hive parquet
table - to keep behaviors consistent.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
