[
https://issues.apache.org/jira/browse/AMBARI-24571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang updated AMBARI-24571:
-------------------------------------
Fix Version/s: 3.1.0
(was: 3.0.0)
> Refactor STOMP events emit approach
> -----------------------------------
>
> Key: AMBARI-24571
> URL: https://issues.apache.org/jira/browse/AMBARI-24571
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.7.0
> Reporter: Papirkovskyy Myroslav
> Assignee: Papirkovskyy Myroslav
> Priority: Critical
> Fix For: 3.1.0
>
>
> Some Ambari functionality is broken without wrapping by STOMP events. We
> should move STOMP events send logic inside of basic operations
> (create/update/delete cluster/components/configs etc.).
> Some things to take care of:
> - we should still support bulk events send.
> - events should be sent AFTER transaction is committed.
> - only topmost operation should send event (e.g. service delete should not
> send delete events for components/etc.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
