Also, to follow on to Matt's answer: If you add your parser this way, then you will have to maintain your own fork of metron, and manage syncing it with apache/metron/master or release. Also, I think it is only implied by Matt, so I will explicitly point out that you will need to build the metron product yourself, and then do installs with YOUR built version of metron to get your parser installed. If not, you will have to do manual steps, one of which will include 'replace the metron-parsers-XXXX.jar on ALL the metron cluster nodes with yours'. METRON-777 provides the foundation for the extension system, and moves the existing parsers over to it. It also introduces the maven archetype. The follow on METRON-942 however provides the REST api support for installing and uninstalling parsers that you create. After 942 lands, your use case will be: * install the mvn archetype * create a directory * run the archetype * re-write the sample parser or replace it ( and the provided unit and integration test/configuration ) * build it * go to the rest page and install it * create a new kafka topic ( rest again ) * create a new storm topology for it ?? ?? Profit.
... View more
