[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671627#comment-16671627
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1249
@ottobackwards I'm not sure what you mean by ingest here? In my head
"ingest" is just getting data into Kafka before the parsers (and really Metron
as a whole) is involved. Could you expand a bit on what you would want each of
those projects to actually contain?
I'm not opposed to organizing things a bit differently, to avoid exploding
things out too much if we add other platforms (especially since it's really not
hard to adjust this PR as needed), but I would have expected something more like
```
.
└── metron-parsers
├── metron-parsers-common
└── metron-parsers-storm
```
> 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)
