[
https://issues.apache.org/jira/browse/METRON-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160317#comment-16160317
]
ASF GitHub Bot commented on METRON-1167:
----------------------------------------
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?
> Define Session Specific Global Configuration Values in the REPL
> ---------------------------------------------------------------
>
> Key: METRON-1167
> URL: https://issues.apache.org/jira/browse/METRON-1167
> Project: Metron
> Issue Type: Improvement
> Affects Versions: 0.4.0
> Reporter: Nick Allen
> Assignee: Nick Allen
> Fix For: Next + 1
>
>
> Many Stellar functions accept configuration values from the Global
> configuration. When using the REPL you can load the global configuration
> values by launching the REPL with the -z option, which loads the global
> configuration stored in Zookeeper.
> The only way to modify the global configuration within the REPL currently is
> to do the following steps.
> 1. Retrieve the global configuration with conf := CONFIG_GET("global")
> 2. Alter that global configuration by modifying the JSON contained in the
> `conf` variable.
> 3. Push the new global configuration using CONFIG_PUT("global", conf)
> 4. Close and then reopen the REPL. Without restarting the REPL the new
> global configuration is not loaded.
> I want a way to do this directly in the REPL, without restarting it, and also
> in a way that does not modify the persisted global configuration in
> Zookeeper. I may be monkeying with something the REPL, but I don't want to
> break one of my live Metron topologies.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
