[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693496#comment-16693496
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1249
I don't have a list, because I honestly hadn't really thought about it
beyond just separating the packages out.
Right now, I think getting rid of the hardcoded test paths is the only
thing that's potentially a direct concern. If we aren't going to do it in this
PR, I can make a jira for it. I personally don't consider it to be essential or
high in my personal priorities (just because it's already like that; if it were
fresh, I'd rather it be not hardcoded).
> 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)
