[GitHub] metron issue #1249: METRON-1815: Separate metron-parsers into metron-parsers...

[justinleet]

Github user justinleet commented on the issue:

    https://github.com/apache/metron/pull/1249
  
    I think everyone's fine with splitting out metron-parsers and 
metron-parsers-common.  I think there's a reasonable argument to give people a 
splitting out point from the basic parsers.  I personally think it's a bit 
overkill, but I'm more than happy to compromise on that.
    
    I think the hangup right now is that in this structure
    ```
    └── metron-parsing
        ├── metron-parsers
        ├── metron-parsers-common
        ├── metron-parsing-common
        └── metron-parsing-storm
    ```
    
    what actually lives in metron-parsing-common if we choose to create it?  It 
seems like the only thing that maybe fits in there is ParserRunner and 
ParserRunnerImpl. Possibly a few other miscellaneous classes. I agree that, 
logically speaking, we could split that out. I just don't think that we need to 
split out such a small module. If, as we start implementing any new platforms, 
there's enough to merit setting up a module, I think it's perfectly fine to do 
it as part of that effort.


---