Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/8800#issuecomment-141254537
Currently `saveAsTable` tries its best to save the table as Hive compatible
format, and falls back to Spark SQL specific format if it fails. I wonder
whether it's too confusing for users to reason about behavior of `saveAsTable`.
Would it be better to have a separate SQL option to force using Hive compatible
format? With this option on, users can be quite confident that if a
`saveAsTable` call succeeds, the saved table must be Hive compatible.
---
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
