diff options
| author | ymqytw <mengqiy@google.com> | 2017-05-10 13:25:06 -0700 |
|---|---|---|
| committer | ymqytw <mengqiy@google.com> | 2017-05-10 13:25:06 -0700 |
| commit | 84c680bc4d43ba680c67e5699189417604e90cb0 (patch) | |
| tree | f728442d4aa08632d5b21acdb9114186ea6adcf4 | |
| parent | 4766413bed8e4275bd2e35769c125faf459d2cab (diff) | |
address comments
| -rw-r--r-- | contributors/design-proposals/multi-fields-merge-key.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/contributors/design-proposals/multi-fields-merge-key.md b/contributors/design-proposals/multi-fields-merge-key.md index bf605d0f..13dcf9ce 100644 --- a/contributors/design-proposals/multi-fields-merge-key.md +++ b/contributors/design-proposals/multi-fields-merge-key.md @@ -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. |