Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13925
Yes @maver1ck I think that's probably a good change, though it may end up
being separate, and related to the isolation level change.
@lihongliustc this PR can be closed. The right solution for this, if any,
is to reduce the transaction isolation level. That seems reasonable to me.
As to the issue of non-transactional RDBMSes seeing partial writes that
can't be rolled back -- the only thing I can see as a solution is to not use
batching, but I think that would run out of memory easily. It may just be how
it is without transactions. The javadoc kind of says as much.
---
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]
