It'll be nice to support CONFIG GET X Y Z... in line with this change #9748
This isn't critical but is kind of expected. Today we support CONFIG GET pattern*, but if we want to be explicit about the configs we need to do multiple calls to CONFIG GET.
The solution should also take into consideration what to do if multiple patterns are passed and if they match the same config more than once..
Comment From: oranagra
maybe we don't want to support multiple patterns? maybe instead respond with an array that doesn't contain the config names, just the value? not sure if we're allowed to do that.
Comment From: zuiderkwast
maybe instead respond with an array that doesn't contain the config names, just the value? not sure if we're allowed to do that.
It would be very strange, because even for a single config (without wildcards) we return the config name already.
127.0.0.1:6379> config get lua-time-limit
1) "lua-time-limit"
2) "5000"
I think allowing multiple patterns and taking care to exclude duplicates would be the more natural solution. Perhaps we can even allow duplicates, since it's an unlikely corner case.
Comment From: oranagra
Yes, I know it'll be strange, and maybe very hard to support for client libraries. I don't think I like it that much. But you have to admit that asking for a single config, and getting back an array with the name and value is annoying (at least in the tcl tests)
Comment From: zuiderkwast
But you have to admit that asking for a single config, and getting back an array with the name and value is annoying (at least in the tcl tests)
I agree, it's an unfortunate design, but inconsistency between singleparam and multiparam would be even more confusing.