Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/1021#discussion_r190011259
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/enrichment/handler/StellarConfig.java
---
@@ -142,8 +143,14 @@ else if(kv.getValue() instanceof List) {
{
--- End diff --
So, what you're trying to solve, I think, is scoped variable resolution. I
think this is a bit of a different use-case here and one that doesn't really
have an analogue in programming languages at large. This is, rather, getting a
list of the variables and their values within the current scope. For our
purposes, though, we only have one scope, global scope. I'd consider
non-global scope resolution to be out of scope for this.
Ultimately, what I'm arguing for is the map variable resolver to have a
special variable that returns the full variable scope.
Is this becoming clearer or am I spreading more mud than I'm clearing?
---
