Github user srowen commented on the issue:
https://github.com/apache/spark/pull/14054
I'm reluctant to add yet another (undocumented) config for another
behavior. Still, it's not that big a deal. My question is: is there a good
reason to employ `SERIALIZABLE`? it means only one partition can be written at
once. We have other destinations that don't have these semantics; even this
output is happy to proceed with no transaction at all. The downside is that
partial writes are observable, but that didn't seem to be the motivation for
using transactions in the first place.
If people are pretty neutral I'd say leave it; if anyone feels fairly
strongly about it I'll just make up some suitable config but leave this new
transaction isolation level as the default.
---
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
