[
https://issues.apache.org/jira/browse/METRON-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522825#comment-16522825
]
ASF GitHub Bot commented on METRON-1634:
----------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1077
@justinleet I changed the logic to reverse the operation rather than
reverting back to a copy. This means that a comment will be removed from the
list on a failed add and a comment will be added back to the list on a failed
remove. The list is sorted by timestamp after a comment is put back to
preserve the order. This should make different add/remove operations
independent of each other. Let me know what you think.
> Alerts UI add comment doesn't immediately show up.
> --------------------------------------------------
>
> Key: METRON-1634
> URL: https://issues.apache.org/jira/browse/METRON-1634
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Priority: Major
>
> For ES (and potentially Solr), when the Alerts UI adds a comment to an alert,
> it calls the update, then immediately calls a findOne to retrieve it. This
> comment might not immediately be available, so it doesn't show the new
> comment.
> Instead of running a findOne, assuming the update responds appropriately, we
> should probably just add it directly in the UI.
> Also applies to removing a comment
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
