Github user merrimanr commented on the issue:

    https://github.com/apache/metron/pull/1213
  
    The latest commit removes the callbacks.  Now the execute method returns a 
list of ParserResult objects.  I had to add a MetronError field to the 
ParserResult class so that both successful messages and errors are passed back.
    
    I also noticed we are currently skipping a tuple if no configuration is 
found for that sensor.  I think skipping the tuple is fine but we should still 
log an error message.  I made a change in the ParserRunner class to throw an 
error on this condition.  The parser bolt will catch it and handle it similar 
to a parser error by creating a MetronError object and sending it to the error 
topic.  Does anyone think we should keep as it is now?


---

Reply via email to