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 useful for
sideloading *other* things (i.e. indexers)
2. When 777 comes in, the user will just adjust to that scheme and delete
the custom sideloaded jars when they decide it makes sense to do so.
To recap, this is just intended to give rudimentary capabilities for the
moment and the sideloading code is intended to be useful beyond sideloading
parsers.
---
