netmap: Allow empty values for unknown parameters in network config #235
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
pool
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-sdk-go#235
Loading…
Reference in a new issue
No description provided.
Delete branch "achuprov/frostfs-sdk-go:feat/unknown_network_info_parameters"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Close #232
Signed-off-by: Alexander Chuprov a.chuprov@yadro.com
[#232] netmap: Allow empty values for unknown parameters in network configto netmap: Allow empty values for unknown parameters in network config@ -50,4 +50,2 @@
switch name {
default:
if len(prm.GetValue()) == 0 {
We are fixing the issue with
MaxECDataCount
but allows to other params be empty when they must be non-emptyDidn't you consider the solution that @dkirillov suggested?
I assume that unknown parameters can be anything, known ones must not be nil. @dkirillov @aarifullin, did you mean a configuration of non-nil params from the application?
If now there are not parameters (which isn't mentioned here) that must not be nil then solution is ok.
Currently devenv sets
SystemDNS
config parameter. Is this parameter one that must not be empty? Is so then we need handle this param. Maybe there are some other parameters that require special treatment.The #232 is more about allow clients don't update SDK when we add new nil parameter. The solution that I suggested just one of many.
Good question. To be honest - I don't know.
For now, I suppose, to keep backward compatibility it's simpler and more correct to ignore values (like in this PR) than to emplace a new parameter name to one of this switch's cases adding some handler.
OK. I am going to resolve this conv