Github user budde commented on the issue:
https://github.com/apache/spark/pull/16797
> Should we roll these behaviors into one flag? e.g.
```spark.sql.hive.mixedCaseSchemaSupport```
That sounds reasonable to me. The only thing I wonder about is if there's
any use case where we want to infer the schema but not attempt to write it back
as a property, say if the external metastore doesn't permit table property
updates from the user. We can always just log the failure, but this could be
noisy for users expecting this behavior by default. This could be solved by
adding an INFER_WITHOUT_SAVING mode.
I'll leave the PR open for now so we can hear and discuss @mallman's input
but if we're all on board with this approach I'll eventually close out this out
in favor of a new PR adding configurable schema inference behavior.
---
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
