Delete support for branch transaction on proxy.
See original GitHub issueReason for deletion:
MANUALXA
in TransactionType does not conform to ShardingSphere’s design specificationTransactionXAHandler
does not conform to ShardingSphere’s design specification.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Astrotomic/laravel-transaction-proxy - GitHub
This example will call the delete() method in a transaction. This is useful if you have any listeners also running database queries, like ......
Read more >Adding an operational branch to support the different WSDL ...
To support the different operations of the WSDL we need different ... Delete the existing routing node by right-clicking on it and then...
Read more >21 Proxy Services: Message Flow - Oracle Help Center
This chapter describes how to create and configure message flows using the Oracle Service Bus Administration Console. Sections include adding and configuring ...
Read more >Enter Transactions screen - Proxy transactions
To change any of this information or to delete the proxy transaction, click the Go To Source button in the Source tab and...
Read more >HTTP-Proxy: Exceptions - WatchGuard Technologies
This topic describes how to use HTTP-proxy exceptions. ... proxy exception, select the Log each transaction that matches an HTTP proxy exception check...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, I understand and
XA protocol in SQL layer
was introudced by https://github.com/apache/shardingsphere/pull/14075. But I think we still need to handleXAStatement
insharding-proxy
especially in the case of crash recovery happening in the multi backend databases. I think we don’t have any test case for this scenario currently.Anyway my +1 for improving the implementation of
TransactionXAHandler
but no just deleting it.no doubt that XA is stands for distribution transaction. I think we just need to figure out how to distinguish between handle it automatically or manually.