[
https://issues.apache.org/jira/browse/METRON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630440#comment-15630440
]
ASF GitHub Bot commented on METRON-295:
---------------------------------------
Github user rkarthik29 commented on the issue:
https://github.com/apache/incubator-metron/pull/338
i am coming in late to this party, but i think the core issue , how would
the bolt know that the script has changed so it can reload the parser. I was
thinking if the previous bolt could add aversion tag to the raw message.. The
parser bolt compares this version or checksum to the last one it had, if
different reruns init and stores this value into the bolt. Else just drops the
version an processes the raw message. A simple checksum may be. Since the
scripts can be really evolved, we could give user more leverage if we allowed
them to keep in HDFS or a filesystem. even a rest api. Please let me know if i
am way off.
> 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)
