Github user viirya commented on the issue:
https://github.com/apache/spark/pull/16797
If the use case where we want to infer the schema but not attempt to write
it back as a property as suggested by @budde, is making sense, then the new SQL
command approach might not work for it. But actually in this case, it is needed
to ask someone who is permitted to migrate and update the table property.
---
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
