[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113589#comment-16113589
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
Will review your other comments shortly. Some additional questions:
I ran the archetype to create a new system parser:
```
[INFO] Parameter: groupId, Value: com.michaelmiklavcic
[INFO] Parameter: artifactId, Value: HelloParser
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: package, Value: com.michaelmiklavcic
[INFO] Parameter: packageInPathFormat, Value: com/michaelmiklavcic
[INFO] Parameter: parserName, Value: hello
[INFO] Parameter: package, Value: com.michaelmiklavcic
[INFO] Parameter: version, Value: 1.0-SNAPSHOT
[INFO] Parameter: metronVersion, Value: 0.4.1
[INFO] Parameter: groupId, Value: com.michaelmiklavcic
[INFO] Parameter: parserClassName, Value: HelloParser
[INFO] Parameter: artifactId, Value: HelloParser
```
Which results in the following directories and files. It seems that
parserName should have been replaced, no?
```
HelloParser/metron-parser-__parserName__
HelloParser/metron-parser-__parserName__/pom.xml
HelloParser/metron-parser-__parserName__/README.md
HelloParser/metron-parser-__parserName__/src
HelloParser/metron-parser-__parserName__/src/main
HelloParser/metron-parser-__parserName__/src/main/config
HelloParser/metron-parser-__parserName__/src/main/config/elasticsearch
HelloParser/metron-parser-__parserName__/src/main/config/elasticsearch/hello_index.template
HelloParser/metron-parser-__parserName__/src/main/config/zookeeper
HelloParser/metron-parser-__parserName__/src/main/config/zookeeper/enrichments
HelloParser/metron-parser-__parserName__/src/main/config/zookeeper/enrichments/hello.json
HelloParser/metron-parser-__parserName__/src/main/config/zookeeper/indexing
HelloParser/metron-parser-__parserName__/src/main/config/zookeeper/indexing/hello.json
HelloParser/metron-parser-__parserName__/src/main/config/zookeeper/parsers
HelloParser/metron-parser-__parserName__/src/main/config/zookeeper/parsers/hello.json
HelloParser/metron-parser-__parserName__/src/main/java
HelloParser/metron-parser-__parserName__/src/main/java/com
HelloParser/metron-parser-__parserName__/src/main/java/com/michaelmiklavcic
HelloParser/metron-parser-__parserName__/src/main/java/com/michaelmiklavcic/hello
HelloParser/metron-parser-__parserName__/src/main/java/com/michaelmiklavcic/hello/HelloParserParser.java
...
```
> 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)
