You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/08 03:41:18 UTC

[jira] [Commented] (METRON-942) REST Support for Parser Extensions

    [ https://issues.apache.org/jira/browse/METRON-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042152#comment-16042152 ] 

ASF GitHub Bot commented on METRON-942:
---------------------------------------

Github user ottobackwards commented on the issue:

    https://github.com/apache/metron/pull/580
  
    Another question here - any parser started from the METRON-UI will not start the next time the service starts.  This problem exists here as well, and should prob. be another jira


> REST Support for Parser Extensions
> ----------------------------------
>
>                 Key: METRON-942
>                 URL: https://issues.apache.org/jira/browse/METRON-942
>             Project: Metron
>          Issue Type: New Feature
>            Reporter: Otto Fowler
>            Assignee: Otto Fowler
>
> If and after METRON-777 lands, support will be required for installing parser extensions into the system, as well as uninstalling them.
> The first step in this is to have support in metron-rest for this.
> The rest interface should support installing a parser extension from the assembly tar.gz produced by the archetype.
> The result of the installation should be:
> * the bundle is installed in the alternate extension library location in hdfs
> * the patterns for all parsers in the extension should be deployed to hdfs
> * the configurations for each pattern should be installed into ZK ( parser, indexing, enrichment )
> * an extension configuration, that includes the parsers it produces, and the default configurations ( the above and elasticsearch etc ) should be entered into ZK
> The reading of these configurations should also be supported.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)