[jira] [Commented] (METRON-1681) Decouple the ParserBolt from the Parse execution logic

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

Github user justinleet commented on the issue:

    https://github.com/apache/metron/pull/1213
  
    Re: callback vs list.  I'm pretty neutral on which one we do. I probably have a slight preference towards the callbacks, just because it more closely matches the original behavior, but I don't think it makes a huge difference in the implementation (and let me know if it does).
    
    @merrimanr Can you look into Travis?


> 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)