[
https://issues.apache.org/jira/browse/METRON-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16636668#comment-16636668
]
ASF GitHub Bot commented on METRON-1798:
----------------------------------------
Github user anandsubbu commented on the issue:
https://github.com/apache/metron/pull/1215
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](https://issues.apache.org/jira/browse/METRON-1802)
so this can be fixed outside of this PR.
> Add mpack support for parser aggregation
> ----------------------------------------
>
> Key: METRON-1798
> URL: https://issues.apache.org/jira/browse/METRON-1798
> 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 at:
> 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
(v7.6.3#76005)
