kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

address comments

This commit is contained in:
ymqytw 2017-05-10 13:25:06 -07:00
parent 4766413bed
commit 84c680bc4d
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
contributors/design-proposals/multi-fields-merge-key.md
View File

@ -40,7 +40,10 @@ If a merge key has multiple fields, it will be a string of merge key fields sepe
If a merge key only has one field, it will be the same as before, i.e. `patchMergeKey:"<key1>"`.
There are no patch format changes.
Additional fields are just extra fields in the patch.
Patches for fields that have multiple fields in the merge key must include all of the fields of the merge key in the patch.
If a new API uses multi-fields merge key, all the fields of the merge key are required to present.
Otherwise, the server will reject the patch.
E.g.
foo and bar are the merge keys.