[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686642#comment-16686642
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1249
It's a bit inelegant, but what if we do something like:
```
└── metron-parsing
├── metron-parsers
├── metron-parsers-common
└── metron-parsing-framework-storm
```
Later we could add metron-parsing-framework-common, etc.
There's still the slight difference between metron-parsing and
metron-parsers, but I think since metron-parsing is the overall parent, and
metron-parsers is just the parsers themselves, it's fairly clear.
Otherwise, someone might need to break out a thesaurus, because I'm awful
at naming things
> 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)
