Feature Description

Currently the vitess driver does not allow commit or rollback a transaction if the request is not from the original connection.

We want to make the Vitess driver be able to commit or rollback a distributed transaction from another connection instead of only allowing from the original connection. To minimize the changes to end user, we can use a config field AllowDistributedTxCommitRollback defaults to False to control the behavior.

I can create a PR to show the idea.

Use Case(s)

We are considering Vitess as our core engine but keep client API the same. Our offering today is a set of RESTful APIs handled by a front end, which then constructs queries and forward to backend databases. Clients do not maintain connection with the front end in any transactions. This means that BEGIN, COMMIT and statements between could come from different front end nodes. That's why we want to allow COMMIT and ROLLBACK from non-original connection.