metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METRON-1681) Decouple the ParserBolt from the Parse execution logic
Date Wed, 03 Oct 2018 14:46:00 GMT

    [ https://issues.apache.org/jira/browse/METRON-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637041#comment-16637041
] 

ASF GitHub Bot commented on METRON-1681:
----------------------------------------

Github user mmiklavc commented on the issue:

    https://github.com/apache/metron/pull/1213
  
    @merrimanr @nickwallen @justinleet - I just want to be sure that I'm following this correctly.
This particular callback appears to be a synchronous, blocking callback. The crux of the implementation
is that you're passing in a function pointer to be executed when the parsing either succeeds
or fails in order to decouple the parsing logic from Storm itself (e.g. tuples, etc.)?


> Decouple the ParserBolt from the Parse execution logic
> ------------------------------------------------------
>
>                 Key: METRON-1681
>                 URL: https://issues.apache.org/jira/browse/METRON-1681
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Justin Leet
>            Priority: Major
>
> Per discussion on https://github.com/apache/metron/pull/1099, there are concerns about
the ParserBolt needed some refactoring.  The discussion didn't hold the PR up, but it was
generally agreed that we should decouple some of the initialization and execution logic.
> This also aids us in integrating with other systems such as NiFi or Spark.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message