[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689461#comment-16689461
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/1249#discussion_r234218876
--- Diff: README.md ---
@@ -132,7 +132,7 @@ component and Apache Kafka as the unified data bus.
Some high level links to the relevant subparts of the architecture, for
more information:
--- End diff --
I'm personally inclined to leave it, because that coupling still exists as
of this PR. I'm inclined to leave it as follow-on for anyone inclined to
decouple our ingest from Kafka. A fair number of our examples and configs are
heavily tied to Kafka right now (e.g. the parser chaining / aggregation), so
I'd be more inclined to have a more thorough decoupling.
Having said that, I'd be more open to changing specific instances if
there's something we feel needs to be changed now.
> 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)
