[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040947#comment-16040947
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/530
Maybe I am misunderstanding the functionality here, but I see a split
looking like this. Of course, you know the work better than me, so maybe there
is a slightly different way we need to tackle this.
(1) PR 1: Introduce bundle/extension mechanism. We would have
unit/integration tests for this functionality. Your manual test steps would
describe step-by-step how to create a parser extension (meaning all the steps
that your Maven plugin automates).
(2) PR 2: Introduce the Maven plugin. You would have unit tests for the
plugin along with a manual test plan describing how a user would go about using
the plugin to create a parser extension.
(3) PR 3: Migrate the parsers to use the bundle/extension mechanism. You
would again have unit/integration tests. Your manual test steps would describe
how to build and deploy the parsers using your extension mechanism.
(4) PR 4: Updates to the Ambari MPack. This just automates some of the
setup steps that were performed manually in the previous PRs.
> 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)
