[
https://issues.apache.org/jira/browse/METRON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630468#comment-15630468
]
ASF GitHub Bot commented on METRON-295:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/338
I'm increasingly becoming of the opinion that the code as it stands is
probably the right path for the the moment. When we are through the changes
from making the grok parser pull from Zookeeper, we can revise if necessary.
The main issue, as I see it, is as @rkarthik29 stated: how do you know that
the scripts changed. And there are now two parsers that need non-trivially
sized external files to function properly, so it may make some sense for there
to be more concerted thought to how to abstract that properly.
> 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)
