[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693467#comment-16693467
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1249
I believe that all the hardcoded paths currently in there are hardcoded
paths that were already there. Currently this PR is limited to rearranging
things + the required changes to reflect that.
Should we be doing that additional refactoring as part of this effort? I'm
not necessarily opposed to taking the opportunity to refactor while it's
already being touched, but it feels like that's conflating what should be two
separate tickets (rearranging the packages and refactoring to remove hardcoded
paths from tests).
> 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)
