[
https://issues.apache.org/jira/browse/METRON-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113529#comment-16113529
]
ASF GitHub Bot commented on METRON-777:
---------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
I see that for parser extensions, the enrichment and indexing
configurations have also been moved into this tree. This structure conflates
parsers, enrichments, and indexing. Beyond that, I also see that we still have
a config directory with zookeeper elements. I'm not sure we want to merge these
concepts together in this fashion. Can you shed some light on this?
```
find extension_etc
extension_etc
extension_etc/parsers
extension_etc/parsers/yaf
extension_etc/parsers/yaf/config
extension_etc/parsers/yaf/config/zookeeper
extension_etc/parsers/yaf/config/zookeeper/parsers
extension_etc/parsers/yaf/config/zookeeper/parsers/yaf.json
extension_etc/parsers/yaf/config/zookeeper/indexing
extension_etc/parsers/yaf/config/zookeeper/indexing/yaf.json
extension_etc/parsers/yaf/config/zookeeper/enrichments
extension_etc/parsers/yaf/config/zookeeper/enrichments/yaf.json
extension_etc/parsers/yaf/config/elasticsearch
extension_etc/parsers/yaf/config/elasticsearch/yaf_index.template
extension_etc/parsers/yaf/patterns
extension_etc/parsers/yaf/patterns/yaf
extension_etc/parsers/yaf/patterns/common
extension_etc/parsers/snort
extension_etc/parsers/snort/config
extension_etc/parsers/snort/config/zookeeper
extension_etc/parsers/snort/config/zookeeper/parsers
extension_etc/parsers/snort/config/zookeeper/parsers/snort.json
extension_etc/parsers/snort/config/zookeeper/indexing
extension_etc/parsers/snort/config/zookeeper/indexing/snort.json
extension_etc/parsers/snort/config/zookeeper/enrichments
extension_etc/parsers/snort/config/zookeeper/enrichments/snort.json
extension_etc/parsers/snort/config/elasticsearch
extension_etc/parsers/snort/config/elasticsearch/snort_index.template
```
and
```
find config/zookeeper/
config/zookeeper/
config/zookeeper/parsers
config/zookeeper/parsers/jsonMap.json
config/zookeeper/indexing
config/zookeeper/indexing/error.json
config/zookeeper/bundle.properties
config/zookeeper/global.json
```
> 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)
