[
https://issues.apache.org/jira/browse/METRON-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272753#comment-16272753
]
ASF GitHub Bot commented on METRON-1339:
----------------------------------------
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/856
So, the scenario here is checking things that *were* valid when uploaded,
but have been invalidated by external changes ( language changes ). I would
like to keep the magic specific.
I think the functionality for the management functions is valid, but can we
do that as a separate Jira/PR? I'll do it, I just want to keep this tight. If
you create the jira and assign it to me that would be super.
I would do the files on disk using the management functions as well.
So we just need to think of the stellar interface for calling
`VALIDATE` with a string, and with a file path. Also saying what
configuration type it is.
Does that make sense?
> Stellar Shell: Should have a way to validate deployed functions
> ---------------------------------------------------------------
>
> Key: METRON-1339
> URL: https://issues.apache.org/jira/browse/METRON-1339
> Project: Metron
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
>
> It is possible that the Stellar Language is changed during a release, meaning
> stellar expressions that are in zookeeper are now invalid, and will not run.
> Currently users cannot verify this without just letting them fail and hunting
> the errors down.
> The Stellar Shell should expose a '%' function that will verify that all
> stellar functions compile and are syntactically correct.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
