Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16938
> CREATE TABLE ... (PARTITIONED BY ...) LOCATION path
I think hive's behavior makes more sense. Users may wanna insert data to
this table and put the data in a specified location, even it doesn't exist at
the beginning.
> CREATE TABLE ...(PARTITIONED BY ...) LOCATION path AS SELECT ...
The reason applies here too.
> CREATE TABLE ... (PARTITIONED BY ...) AS SELECT ...
When users don't specify the location, mostly they would expect this is a
fresh table and the table path should not exist.
---
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
