[
https://issues.apache.org/jira/browse/METRON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832447#comment-16832447
]
Tibor Meller edited comment on METRON-1856 at 5/3/19 11:59 AM:
---------------------------------------------------------------
_*> What happens if you try to group 3 parsers that are already running? Or
some combination of running and not running?*_
[~ottobackwards] I think these are very good edge case we need to cover.
What [~ruffle1986] saying is UI not allows the user to combine running and
stopped parsers. Hower only ignoring the interaction to prevent the user from
doing this is not a good approach.
I suggest notifying the user on the UI about the fact that he/she tries to
combine running and stopped parser and offer to stop parsers impacted by
his/her interaction. After that intermediate step, we can let the user follow
the normal grouping workflow with stopped parsers.
was (Author: tibormeller):
[~ottobackwards] I think these are very good edge cases we need to cover.
What [~ruffle1986] saying is UI not allows the user to combine running and
stopped parsers. Hower only ignoring the interaction to prevent the user from
doing this is not a good approach.
I suggest notifying the user on the UI about the fact that he/she tries to
combine running and stopped parser and offer to stop parsers impacted by
his/her interaction. After that intermediate step, we can let the user follow
the normal grouping workflow with stopped parsers.
> [UI] Implement parser grouping with drag and drop
> -------------------------------------------------
>
> Key: METRON-1856
> URL: https://issues.apache.org/jira/browse/METRON-1856
> Project: Metron
> Issue Type: New Feature
> Reporter: Tibor Meller
> Priority: Major
> Attachments: create-parser-group.gif, delete-parser-group.gif,
> merge-and-create-new-group.gif, save-parser-group.gif
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The capability to group parsers via the CLI already exists in Metron, but it
> currently is not possible to do so through the Management UI. This feature
> seems important as it allows users to pass in groups of parsers to start,
> stop, disable and enable rather than enacting the action on each individual
> parser.
> An initial implementation of the UI was done by Tamás Fodor, Tibor Meller and
> myself (@ruffle1986, @tiborm and @sardell on GitHub, respectively), and the
> REST endpoint work was performed by Ryan Merriman in PR 1396:
> [https://github.com/apache/metron/pull/1396].
> Here is a brief description of the UI changes we proposing (and subsequently
> implemented in PR 1360).
> In order to create a parser group, simply drag and drop two parsers together.
> A user can optionally update the name and add a description before creating
> the group. Notice that once a group is created, the parser group is
> highlighted in green and the parsers moved inside of a group are highlighted
> in yellow.
> !create-parser-group.gif|width=601,height=330!
> Once a user has created the parser groups they want, they can simply click on
> the apply button at the bottom of the screen. You'll notice the highlighting
> colors go away, a success message appears and controls for all the parsers in
> the group are available at the group level (in this case the start button).
> !save-parser-group.gif|width=601,height=330!
> If a user wants to add to a group or create a new group from nested parsers,
> they can choose to either merge or create a new group as shown below.
> !merge-and-create-new-group.gif|width=601,height=330!
> If a user wants to delete a group, they can simply click on the trash can
> icon in the group's controls section. We chose to keep the confirmation popup
> in addition to the apply button in order to prevent accidental group
> deletions and prevent sending multiple http delete calls one after the other
> to the backend. If a user decides not to delete a group after confirming with
> the modal window, they can click on the discard button to return to the
> previous state.
> !delete-parser-group.gif|width=601,height=330!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
