Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/1213
The latest commit resolves the conflicts introduced by
https://github.com/apache/metron/pull/1184. The changes in all classes except
ParserRunnerImpl and ParserRunnerImplTest were fairly trivial, mainly just
adjusting the return types to match the new MessageParserResult and
ParserRunnerResults interfaces.
Most of the work was done in ParserRunnerImpl (the execute method
specifically). Since the MessageParser interface can now return multiple
messages and exceptions (and a master exception in some cases), there needs to
be a way to map them to a ParserRunnerResults object (which is a list of
messages and errors). Now the primary job of this execute method is to:
- call MessageParser.parseOptionalResult
- post process messages returned by the MessageParser
- consolidate the various errors and messages into a single
ParserRunnerResults object
Let me know if anyone thinks this should work differently. I also added
more javadocs to the various classes involved, primarily ParserRunnerImpl since
that's where the magic happens. This merge was fairly significant so I am
planning on testing in full dev again.
---
