[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968327#comment-15968327
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/530
Woah, big contribution here; thanks @ottobackwards ! So this one is hard
to review because a lot of it is:
* Copied from NiFi's nar
* Moving files around.
Would you mind giving us a list of files where changes are made that don't
fit those two categories? I think that'd help us isolate the bits to review
easier.
In the meantime, I have a couple of questions:
* Could you go over again why we needed the VM in travis?
* What is the parser file size impact? In other words, when we create a
new bundle for a parser, are we shading and including all of metron-parser or
is that isolated from the parser?
> 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)
