Do not use packed repeating fields for copies numbers #30
Labels
No labels
P0
P1
P2
P3
good first issue
triage
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api#30
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Is your feature request related to a problem? Please describe.
#17 introduces copies number as a
repeated
field in the protocol. There is a compatibility issue with it which can be mitigated.Proto3 uses packed repeated fields by default for scalar types, e.g. numbers. It means that there is a difference in wire code for one repeated number and just one number.
This is incompatible change and it breaks signature checks.
Describe the solution you'd like
Disable packing for the copies numbers.
Describe alternatives you've considered
Ignore this because protocol compatibility is already broken with the #25.
/cc @realloc @fyrchik
Do not use packed repeating fields for copies numbers.to Do not use packed repeating fields for copies numbersWill be handled in future compatibility breaking API versions.