[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671658#comment-16671658
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1249
I guess what I mean is that there will be or may be common things that
aren't related to parsers, but are related to storm + spark etc. Ingest is the
wrong word.
```bash
└── metron-parsing
├── metron-parsers
├── metron-parsers-common
├── metron-parsing-common
└── metron-parsing-storm
```
maybe this is better.
Also, it may be that there is shared storm/spark code between all our
topologies that shouldn't be buried in parsers.
> 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)
