Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14086
- `DROP`/`CREATE`/`DELETE` can be rolled back. In Oracle, we are unable to
roll back `TRUNCATE`. I am not sure whether this is a big deal to the Spark
users.
- If the data source is `PostgreSQL`, we also truncate all its descendant
tables by default. This side effect does not look good to me. Not sure whether
the Spark users can tolerate it.
- So far, Spark does not have role-based privilege. It completely depends
on the underlying data sources. If DBAs have to grant higher privileges to
Spark app (for any reason), this change could be a potential issue.
I did not investigate all the RDBMS vendors and different versions might
have different behaviors. My suggestion is to do more investigation before
adding this support.
---
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]
