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

[merrimanr]

Github user merrimanr commented on the issue:

    https://github.com/apache/metron/pull/1249
  
    Following along here.  I'm in agreement with @ottobackwards's point about 
not having to depend on the module that contains all the parsers that ship with 
Metron.  So having a separate `metron-parsers` and `metron-parsers-common` 
makes sense to me.  
    
    I'm not understanding what would go in `metron-parsing-common` though.  
Maybe @ottobackwards is correct and there is shared code between storm/spark.  
But wouldn't that belong in `metron-parsers`?  I feel like the right approach 
will come into focus after we take an initial pass at splitting things up.  I 
propose we start with:
    ```
    └── metron-parsing
        ├── metron-parsers
        ├── metron-parsers-common
        └── metron-parsing-storm
    ```


---