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.
---