[
https://issues.apache.org/jira/browse/METRON-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16302220#comment-16302220
]
ASF GitHub Bot commented on METRON-295:
---------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/338
Re-reading this, I think it is dead, unless there is an update triggered by
this.
I *think* I have the resolution to the update issue.
Post `777` and parser extensions, extensions can / will be deployed through
the ui.
A script parser will deploy scripts, as we do grok rules to a directory, we
can have the deployment *also* make an entry in zookeeper with the checksum of
the script or some such. __That__ can be the item that is in zookeeper and
monitored for change. If we deploy a new version of the script by installing
it in the UI, it will save it to hdfs, and the change the entry in zookeeper,
triggering reload.
If this PR *is* dead, I may take this up
> 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.2BETA
> 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.4.14#64029)
