metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (METRON-1681) Decouple the ParserBolt from the Parse execution logic
Date Tue, 02 Oct 2018 13:29:00 GMT


ASF GitHub Bot commented on METRON-1681:

Github user justinleet commented on the issue:
    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
    @merrimanr Can you look into Travis?

> Decouple the ParserBolt from the Parse execution logic
> ------------------------------------------------------
>                 Key: METRON-1681
>                 URL:
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Justin Leet
>            Priority: Major
> Per discussion on, 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

View raw message