[
https://issues.apache.org/jira/browse/METRON-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679823#comment-16679823
]
ASF GitHub Bot commented on METRON-1815:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1249
@ottobackwards I was sick the past couple days, so sorry about the delay in
responding.
Hopefully, what we're saying is, for this PR, refactor this to
```
└── metron-parsing
├── metron-parsers
├── metron-parsers-common
└── metron-parsing-storm
```
Where metron-parsers-common contains the various utils, plus the building
block parsers (e.g. Grok). Whenever another platform gets added, it would go
in "metron-parsing-<platform>" and they can create "metron-parsing-common" if
needed (because right now it would be empty).
Sound like a plan?
> 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)
