[
https://issues.apache.org/jira/browse/METRON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651256#comment-15651256
]
ASF GitHub Bot commented on METRON-295:
---------------------------------------
Github user rkarthik29 commented on the issue:
https://github.com/apache/incubator-metron/pull/338
I think that should be a separate lira. This feature does a very simple
thing, it allows for a use to provide a function in the format JsonObject
parse(rawMessage) in a language of his choice. The concept is that he can now
use standard library functions to parse the rawMessage into JSon, which metron
can then use.
dependencies for external libraries i think will need to be tested. This
could be the strategy...
1. For JS script, you could just include the min.js link or just put your
script in a http server and refer it in the script.
2. For groovy script, could be as simple as dropping a jar in the proper
location, i guess the bolt class path.
3. for python, i think we should be able to put the modules in a modules
folder and i think python script can refer to it from there, we will have to
look at that packaging.
I think it is a little more complicated and i think a separate would be
needed to track it.
> Script parsing bolt
> --------------------
>
> Key: METRON-295
> URL: https://issues.apache.org/jira/browse/METRON-295
> Project: Metron
> Issue Type: New Feature
> Affects Versions: 0.2.1BETA
> Reporter: James Sirota
> Assignee: Karthik Narayanan
> Priority: Minor
> Labels: newbie, platform
> Fix For: 0.2.2BETA
>
>
> In addition to having a Grok parsing bolt we need a bolt that can execute a
> script in order to parse a telemetry. This way you can still script the
> parsing for telemetries for which Grok expressions are too complex, but still
> don't have to define a java parser
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
