[
https://issues.apache.org/jira/browse/METRON-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16330816#comment-16330816
]
ASF GitHub Bot commented on METRON-1090:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/687
Agreed, this is a POV issue. Though from the user perspective they aren't
distinguishing between "this is in the REPL" vs "this is in the enrichment
topology", so I think we do need to manage the experience if we're moving
functionality from the MACHINE to the LANGUAGE to ensure it's consistent.
Beyond that, it's unclear whether we need an resolver `update` function as
part of THIS PR, but I think we very much *will* need it if we decide to make
stellar multi-expression. I suspect we should punt on it until that effort.
> STELLAR Add Assignment capability to Stellar language
> -----------------------------------------------------
>
> Key: METRON-1090
> URL: https://issues.apache.org/jira/browse/METRON-1090
> Project: Metron
> Issue Type: New Feature
> Reporter: Otto Fowler
> Assignee: Otto Fowler
> Priority: Major
>
> Add support for =, +=, -=, *=, /= for variables in stellar.
> foo = 5 returns 5 AND sets foo to 5 if the VariableResolver supports it.
> The shell should be changed to assign variables using this syntax, because
> exposing the left side to stellar allows catching errors for invalid keywords
> in left side.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
