[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040886#comment-16040886
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/530
@ottobackwards I definitely agree that we need more documentation around
absolutely everything you listed. The main reason I want the outline for
adding a new parser is just so I have a way to actually get a good handle on
what's going on to be able to review it. It would be super helpful to even
have a basic outline of how to do it. I assume @nickwallen feels the same way.
For a first pass, I don't know that this needs to be absolutely point by
point detailed, but at least enough for people to dig in and get started. I
personally think it's reasonable to have the point by point detailed, nicely
formatted version be a follow-on, but just something basic and (mostly) correct
is what I personally want to see.
> Create a plugin system for Metron based on 'NAR'
> ------------------------------------------------
>
> Key: METRON-777
> URL: https://issues.apache.org/jira/browse/METRON-777
> Project: Metron
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> The success of the Metron project will be greatly dependent on community
> participation, and with that the ability to adapt and extend Metron without
> having to maintain a fork of the project.
> As organizations and individuals look to extend the Metron system with custom
> parsers, enrichments, and stellar functions that may be proprietary in
> nature, the ability to develop and deploy these extensions outside the Metron
> code base is critically important.
> To that end, and after community discussion and proposal we create or
> formalize the 'plugin' development story in Metron.
> The proposal is to adapt the Apache Nifi NAR system for use in Metron. This
> will provide the system with:
> * archetype(s) for developer projects and independent development
> * defined packaging and metadata for 'plugin' products
> * loading and instantiation with classloader isolation capabilities
> * removing the necessity for shading plugin jars
> These capabilities will also enable other features, such as plugin lifecycle,
> plugin configuration+redeployment, and other things.
> The plugin archetypes and their installation will be a followon
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
