Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/740
So the GLOBAL_CONFIG is used when setting up stellar in a few places, and
used in a couple of functions to determine what they return. And may be used
by other functions in the future both Metron's or UDFs.
I am asking about co-opting this flag, and if we have thought about any
unwanted consequences from this now or in the future, based on the intent of
the flag.
Is the scope of that flag only the shell? Will the functions see it? If
they do, and they expect a field to be set in the config, but it is not because
the shell only set one property that the user did set, what will the behavior
be?
We may be able to say "Well, right now non of the functions that depend on
that flag and specific properties will be called from the shell". But what
keeps someone from writing a UDF that depends on that flag from breaking in the
shell because they don't understand that we do this?
---
