Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14054
Interesting, well maybe `READ_UNCOMMITTED` is still a pretty good setting,
because the transaction here doesn't even read anything and doesn't care about
what it might read, but sounds like it could be promoted anyway.
Yes, how about using the specified isolation level if available, and
falling back to just leaving the default if not available, but transactions are
supported in general. I like that as it is more robust.
---
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
