[
https://issues.apache.org/jira/browse/SCB-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559558#comment-16559558
]
ASF GitHub Bot commented on SCB-692:
------------------------------------
coveralls commented on issue #231: SCB-692 Recovery the old-saga implementation
URL:
https://github.com/apache/incubator-servicecomb-saga/pull/231#issuecomment-408383920
[](https://coveralls.io/builds/18194747)
Coverage increased (+1.3%) to 94.246% when pulling
**5ccff0410723702cea117b08c65aa7c77ec9e0a9 on SCB-692** into
**10e1f95406f1c8a6cc6db14b632dfcf14ebeb45b on master**.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Restore the centric Saga
> ------------------------
>
> Key: SCB-692
> URL: https://issues.apache.org/jira/browse/SCB-692
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Saga
> Reporter: Willem Jiang
> Priority: Major
>
> As we are working with Sharding-Sephere to provide the Saga executor engine
> in the Sharding-Proxy. The old saga executor can be use to coordinate the
> transactions across the database or the transactions.
> We need to extends the Saga invocation (transport) to support the MySQL calls
> or the other PRC calls.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
