[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673131#comment-16673131
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1249
Is there anything specific you'd want to pull out?
Looking at the code right now, parsers-common contains
* asa
* bro
* cef
* csv
* filters
* fireeye
* interfaces
* ise
* json
* lancope
* logstash
* paloalto
* snort
* sourcefire
* syslog
* utils
* websphere
along with some miscellaneous utilities and ParserRunner and such.
metron-parsers-storm contains
* bolt
* topology
I could see doing the split you mention, but right now I don't see anything
that would obviously go in, unless we wanted to split the actual parsers
themselves out from parsers-common. I'm not opposed to that, but it seems like
overkill with what we have right now (although I admittedly may eat those words
when actually adding a for real Storm alternative). Mostly, splitting out the
Storm bits seems like it results in an empty metron-parsing-common and the same
metron-parsing-storm.
> Separate metron-parsers into metron-parsers-common and metron-parsers-storm
> ---------------------------------------------------------------------------
>
> Key: METRON-1815
> URL: https://issues.apache.org/jira/browse/METRON-1815
> Project: Metron
> Issue Type: Improvement
> Reporter: Justin Leet
> Assignee: Justin Leet
> Priority: Major
>
> In order to expose our parsers to 3rd party components (e.g. the discussions
> on NiFi and potentially other platforms like Spark), we should
> separate the storm-bits into its own project. The metron-parsers-common
> project should contain only parser-oriented code, whereas the
> metron-parsers-storm project should contain the storm specific code
> (e.g. the parser bolt).
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
