Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/14054
`READ_UNCOMMITTED` is applicable to read-only transactions. Normally, the
RDBMS will promote it to the higher/restricter isolation level if users try to
apply `READ_UNCOMMITTED` to insert, delete or updates. This is what happens
inside RDBMS. Thus, I think we should remove this option for our insert-only
workloads.
In addition, I am not sure whether we should call
`supportsTransactionIsolationLevel` before using the isolation levels.
---
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
