[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040848#comment-16040848
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/530
> @nickwallen: Or did you submit this to get buy-in as a proof-of-concept,
that we can then break down into multiple, smaller PRs, get reviewed and then
merged into master?
I feel like the second would be a good approach for this one.
> @ottobackwards: The answer is 1. I did not submit until this set of
functionality was done because it is completely end to end testable.
I really think we should break this apart into multiple PRs. Each with
their own documented test plan. I don't think we are going to get a review of
sufficient quality without it. I am open to however you think it should be
broken apart and can offer my own suggestion on breaking it apart should you
need.
> 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)
