[jira] [Commented] (METRON-1230) As a stopgap prior to METRON-777, add more simplistic sideloading of custom Parsers

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

Github user cestella commented on the issue:

    https://github.com/apache/metron/pull/785
  
    @ottobackwards  One of the reasons why I did it the way that I did (hook into the way the storm accumulates the jar to submit) was that:
    1. while it's useful for sideloading parsers, it's also useful for sideloading *other* things (i.e. indexers)
    2. When 777 comes in, the user will just adjust to that scheme and delete the custom sideloaded jars when they decide it makes sense to do so.
    
    To recap, this is just intended to give rudimentary capabilities for the moment and the sideloading code is intended to be useful beyond sideloading parsers.


> As a stopgap prior to METRON-777, add more simplistic sideloading of custom Parsers
> -----------------------------------------------------------------------------------
>
>                 Key: METRON-1230
>                 URL: https://issues.apache.org/jira/browse/METRON-1230
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Casey Stella
>
> Until we get 777 in, it'd be nice to have a simple ability using the normal storm functionality to enable users to provide custom parsers without forking Metron.  This should be done via simply creating a jar with their code (and bundled dependencies) and have it picked up and available to the REST Service (and consequently the management UI) as well as the start_parser_topology.sh command.
> This should be minimal movement as we have a more robust solution coming with METRON-777.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)