[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675517#comment-16675517
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1249
I can't think of any... I'm trying to point out where I think it would go
when it exists. The parsing-common will come out of the 'second' host
platform.
I think the rules of why what goes where are the important thing. So I
shouldn't have to include all the parsers just to create a new csv parser, I
shouldn't have to include spark and or storm to create a foo host....
> 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)
