There were some questions in #1576 regarding if the FIRST time someone creates lookups could be smarter about handling null values in the configuration.
The MVP solution is to require an empty map {} be posted to the configuration in order to override a NULL config value.
This ask is that the QTL dynamic config has a more straight forward methodology for handling its first-time initialization
Such initialization should make ABSOLUTELY SURE that there is not an error case where a configuration in the metadata can be overwritten by a race between proper initial population of local metadata cache, and writing of the new config to the metadata store.
There were some questions in #1576 regarding if the FIRST time someone creates lookups could be smarter about handling null values in the configuration.
The MVP solution is to require an empty map
{}be posted to the configuration in order to override a NULL config value.This ask is that the QTL dynamic config has a more straight forward methodology for handling its first-time initialization
Such initialization should make ABSOLUTELY SURE that there is not an error case where a configuration in the metadata can be overwritten by a race between proper initial population of local metadata cache, and writing of the new config to the metadata store.