[
https://issues.apache.org/jira/browse/METRON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15630527#comment-15630527
]
ASF GitHub Bot commented on METRON-295:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/338
@rkarthik29 One of the advantages of keeping the configuration (scripts in
this case) in Zookeeper is that you get notified when something changes. You
don't need to track versions. Unfortunately, until #308 gets merged in, the
ParserBolt does not notify the parser class that the config has changed and
only provides the configuration on startup (hence the need to restart the
topology).
I think it makes sense to keep it in HDFS for this PR and accept the
current restriction of having to restart the topology for it to take effect.
Until we merge #308 or agree on the another approach, I wouldn't worry about
script changes being updated on the fly. There has already been a lot of
discussion and work put into this so it doesn't make sense to start over. We
could even update #308 to include this parser once we get closer to merging
that.
> 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)
