[
https://issues.apache.org/jira/browse/SCB-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16889513#comment-16889513
]
Daniel Qian commented on SCB-1386:
----------------------------------
I think Alpha doesn't work that way. Alpha doesn't know what Local Tx are
involved in Saga in advance. It just know what happened, can't know what not
happened.
I started a discussion about async support for saga on apache mail list and
give some thoughts:
[https://lists.apache.org/thread.html/33aa0d9827cf10933796971ebe20cd47205fac8011fba32c5d03a222@%3Cdev.servicecomb.apache.org%3E]
> @SagaEnd annotation
> -------------------
>
> Key: SCB-1386
> URL: https://issues.apache.org/jira/browse/SCB-1386
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Saga
> Affects Versions: pack-0.5.0
> Reporter: José Cardoso
> Priority: Major
>
> In an async environment (ex: microservices architecture communicating via
> messaging systems) it is important to control when the saga ends. Therefore,
> I propose a new annotation - @SagaEnd - to have the possibility to explicitly
> end the Saga, which will also allow the triggering of the compensation
> methods in case of failure.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
