[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693628#comment-16693628
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/1249
Sorry to beat a dead horse, but I was giving this a once over and saw
`metron-parsing-framework-storm`. Could we go with the more concise
`metron-parsing-storm`?
I'd prefer this because it matches what we already have in the Profiler;
`metron-profiler-common`, `metron-profiler-spark`, `metron-profiler-storm`,
`metron-profiler-repl`. I'd like to keep the same convention for naming
projects.
We've already decided that the words`parsing` and `parsers` are different
enough to denote the differences between the projects. I don't see any new
information being conveyed by the word 'framework'. IMHO.
> 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)
