Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/1249
The common should have all the interfaces, base classes and utilities.
The parsers should only have the parsers.
In 777 I left the Grok, JSON, CSV in common, and only had the derived split
out. I don't think that is necessary, but we may want to think about it from a
library design pov. Why would I have to use both metron-parsers and
metron-parsers common just to create my own grok derivative for example.
I think that the idea should be " a third party should never have to depend
on metron-parsers unless they are deriving from a specific parser type - ASA,
YAF, BRO. Deriving from a 'base format type' ( GROK, csv, json, syslog ) only
requires dependency on common"
---
