metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ottobackwards <...@git.apache.org>
Subject [GitHub] metron pull request #530: METRON-777 Metron Extension System and Parser Exte...
Date Thu, 08 Jun 2017 01:58:50 GMT
Github user ottobackwards commented on a diff in the pull request:

    https://github.com/apache/metron/pull/530#discussion_r120784845
  
    --- Diff: metron-extensions/metron-parser-extensions/metron-parser-bro-extension/metron-parser-bro/src/main/config/zookeeper/enrichments/bro.json
---
    @@ -0,0 +1,17 @@
    +{
    +    "enrichment" : {
    --- End diff --
    
    OK.  This is important.  A parser developer who is developing and maintaining their own
parsers outside the metron tree should not have to makes changes to the metron code tree.
 Ever.
    
    As an extension developer, I want my extension to be a manageable, singular entity.  The
packaging should contain everything todo with my extension.   I would ask back, why when I
create an extension would I **not** have all the configurations and bits together?
    
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message