Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16019
so the actual difference is, if the table exists and `ignoreIfExists` is
true, previously we will still try to create this table, but logically we
should do nothing.
Since we are revisiting it, I have some more thoughts. If the table already
exists and `ignoreIfExists` is false, we will throw exception at spark side.
However, if the table doesn't exist at the beginning, and get created right
after the if check in `HiveExternalCatalog.createTable`, then we will throw
exception at hive side. Shall we unify this and let hive metastore to handle
`ignoreIfExists`?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
