[
https://issues.apache.org/jira/browse/METRON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630122#comment-15630122
]
Karthik Narayanan commented on METRON-295:
------------------------------------------
Just created a PR for this Metron 295 #338.
https://github.com/apache/incubator-metron/pull/338
Create a Base ScriptParser class in matron-parsers. A parserconfig will allow
the user to set the path, language and function name for his parser.
"parserConfig": {
"path": "location of script”,
“language”:js/python/groovy”,
“parsefunction”:”default is parse "
... other optional fields
}
The function in the script will take in a single argument which is the
rawMessage and will return a map or dict object.
ScriptParser also looks for any common functionality in the
/scripts/<language>/common location. This is similar to the GrokParser
behavior. This common location can be used for utility functions and methods.
> 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
>
> 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)
