[
https://issues.apache.org/jira/browse/METRON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651289#comment-15651289
]
ASF GitHub Bot commented on METRON-295:
---------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/incubator-metron/pull/338
So that is similar to the pyleus stuff. Although pyleus actually produces
jar topologies as a unit. The question is, with only standard library support
for any of these languages how useful is this? Does that need to be accounted
for now or can it be another jira as you mention. I'm not advocating either
way, but if we do say it will be another jira, and there will be further work
here, we should explicitly state that and create the jiras to put that plan in
place.
> 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)
