[
https://issues.apache.org/jira/browse/METRON-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198873#comment-16198873
]
ASF GitHub Bot commented on METRON-1232:
----------------------------------------
Github user iraghumitra commented on a diff in the pull request:
https://github.com/apache/metron/pull/787#discussion_r143772168
--- Diff: metron-interface/metron-alerts/src/app/service/update.service.ts
---
@@ -32,13 +33,31 @@ export class UpdateService {
defaultHeaders = {'Content-Type': 'application/json',
'X-Requested-With': 'XMLHttpRequest'};
+ alertChangedSource = new Subject<PatchRequest>();
+ alertChanged$ = this.alertChangedSource.asObservable();
constructor(private http: Http) { }
public patch(patchRequest: PatchRequest): Observable<{}> {
let url = '/api/v1/update/patch';
- return this.http.patch(url, patchRequest, new RequestOptions({headers:
new Headers(this.defaultHeaders)}))
- .catch(HttpUtil.handleError);
+ let observable = Observable.create((observer => {
--- End diff --
@merrimanr This is not an anti-pattern as such, we can trigger the event
from the component that is trying to patch, but it has to be done at all places
wherever we are patching. In this way there is no such need and list view will
definitely get intimated of all changes.
If you are not comfortable we can change it :)
> Alert status changes are not reflected in list view
> ---------------------------------------------------
>
> Key: METRON-1232
> URL: https://issues.apache.org/jira/browse/METRON-1232
> Project: Metron
> Issue Type: Bug
> Reporter: RaghuMitra
> Assignee: RaghuMitra
>
> When escalating an alert (changing its status), the list view does not
> reflect the change until a refresh occurs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
