Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/785
well then.
In a world where 777 didn't exist I would be a +1.
In world where 777 does exist, i'm a +0, since I feel the effort would have
been better spent reviewing 777, but think
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/785
@ottobackwards One of the reasons why I did it the way that I did (hook
into the way the storm accumulates the jar to submit) was that:
1. while it's useful for sideloading parsers, it's also us
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/785
So, when 777 hits, this is going to be removed?
---
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/785
The only real change here is the addition of a Transformer that hooks into
Storm's `storm jar` command and will merge the dependent jars. This was done
so that we could avoid touching the Parser in
