Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1099
Happy to help explain it, and it's really helpful to get feedback on it
because it led to improved docs, so hopefully it makes sure things are clearer
to anyone looking at this later.
I created tickets for:
- [Management UI changes for sensor
aggregation](https://issues.apache.org/jira/browse/METRON-1678)
- [REST changes to support parser
aggregation](https://issues.apache.org/jira/browse/METRON-1679)
- [Allow the option for intermediate kafka topics to be removed in
aggregated sensors](https://issues.apache.org/jira/browse/METRON-1682)
- [Allow Ambari to accept quoted parser
groups](https://issues.apache.org/jira/browse/METRON-1680)
- [Decouple the ParserBolt from the Parse execution
logic](https://issues.apache.org/jira/browse/METRON-1681)
I held off on creating a ticket for the routing process applying a
transform. @ottobackwards Would you mind creating that, to make sure the use
case and examples or assumption, etc. are what you expect?
---
