Allow updateMask to be set for Patch/Updating documents
See original GitHub issueCurrently updateDocument behaves exactly like createDocument, and will always overwrite the document if it exists, and create a new one if it doesn’t.
Adding this functionality will allow users to update certain fields and ignore others. A true “patch”.
Details can be found in the docs: https://cloud.google.com/firestore/docs/reference/rest/v1beta1/projects.databases.documents/patch#query-parameters
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:9 (7 by maintainers)
Top Results From Across the Web
ee.Image.updateMask - Earth Engine - Google Developers
New mask for the image, as a floating-point value in the range [0, 1] (invalid = 0, valid = 1). If this image...
Read more >Storage Transfer Service transferJobs.patch API does not ...
Changing that line to updateTransferJobFieldMask: transferSpec should work. From the documentation: The field mask of the fields in transferJob ...
Read more >Solved: Update Data Masking - Google Cloud Community
Solved: Hello, I triying Data Masking, with this documentation: ... Set the updateMask query parameter to specify a field mask that includes a ......
Read more >Patch feature | gRPC-Gateway - GitHub Pages
The HTTP PATCH method allows a resource to be partially updated. ... In this case, the FieldMask is updated from the request body...
Read more >Method: projects.locations.deliveryPipelines.patch
The fields specified in the updateMask are relative to the resource, ... For help, check the APIs Explorer documentation. Request parameters.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Available in v22! 🎈
So I see pros and cons both ways, but for the sake of backwards compatibility, I went with your original suggestions.