[jira] [Commented] (METRON-777) Create a plugin system for Metron based on 'NAR'

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111319#comment-16111319 ] 

ASF GitHub Bot commented on METRON-777:
---------------------------------------

Github user mmiklavc commented on the issue:

    https://github.com/apache/metron/pull/530
  
    I'm back to looking through this again. A couple questions:
    1) I was under the impression that our local copy of the nar functionality would be a hard fork that would naturally deviate from the NiFi based on our own requirements. In fact, I thought the entire reason for our fork was because of features we needed that did not make sense for NiFi. Do we really want to consider pulling patches going forward? I'm also in support of keeping bundles-lib and bundles-maven-plugin at the top level, per @mattf-horton's comments, though I don't think we want to have to worry about merges and cherry-picking commits, especially since we forked local. Just a thought.
    2) Regarding the bundle loading, have you looked at the work from https://github.com/apache/metron/pull/468 for loading from HDFS? Any overlap there?
    
    Since this is a relatively large chunk of functionality, I decided that my testing methodology for this feature should be use case driven. I'll report back with what I intend to work through and @ottobackwards can let me know if I've missed or misinterpreted any aspects of this PR in those use cases/tests.


> 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.4.14#64029)