metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (METRON-1798) Add mpack support for parser aggregation
Date Wed, 03 Oct 2018 09:20:00 GMT


ASF GitHub Bot commented on METRON-1798:

Github user anandsubbu commented on the issue:
    Hi @nickwallen , thank you for the review.
    > @nickwallen One thing I notice right off is that we did not add any documentation
for the parsers fields in Ambari. Would it make sense to add a brief description to the pop-up
text describing how a user can define parsers?
    Sure, makes sense. I have also added a section to the Parser Chaining README as well with
examples. Please have a look.
    > @nickwallen: When switching parser topologies, some of the original parser topologies
can fail to be shut down properly.
    > I have found that the same issue occurs in master. Since that is the case, we could
choose to tackle this as a separate ticket. It is your choice.
    I created [METRON-1802]( so this can
be fixed outside of this PR. 

> Add mpack support for parser aggregation
> ----------------------------------------
>                 Key: METRON-1798
>                 URL:
>             Project: Metron
>          Issue Type: Task
>            Reporter: Anand Subramanian
>            Assignee: Anand Subramanian
>            Priority: Major
> Support spawning of storm topologies if a user specifies an aggregated parser configuration
> Ambari -> Metron -> Configs -> Parsers -> "Metron Parsers"
> For example, specifying the following:
> "bro,snort,yaf", "snort,yaf", yaf
> should spawn an aggregated topology for first two, and a regular topology for the 'yaf'.

This message was sent by Atlassian JIRA

View raw message