[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16040878#comment-16040878
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@nickwallen WRT Test plan:
Do we have a generic smoke test plan? If so, then I'll reference it. If
not I will spell it out more clearly.
There are, I think two aspects to this that I would like to detangle.
From a 'how metron works' point of view, this change does not change what the
system does in an observable way, it retains the status quo ante functionality.
So that test plan is not different than another change that says "run up in
full dev and verify that that topologies are running etc....". That being
said, I will list it out in more detail. I apologize for the vagueness. The
other point of view, which I think you are referencing is "as a metron
developer, who may have to add a new parser to metron proper". This **is**
different from before, but was also not documented in the old architecture
either, which is why I didn't take a stab at the dev guide in this PR. We also
do not have guides for adding new ambari services, adding components to the
rpm, creating new ambari scripts as well, all things I had to reverse and
figure out to get this working, and we did not hold up those efforts to wait
for them, so I did not think it was required.
That is not to say that I don't agree such things should exist, and maybe
should have been required then and be required now. I will certainly take a
stab at it
> 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)
