We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The following request:
{ "mode": "NON_TRANSACTIONAL", "mutation": { "insertAutoId": [ { "key": { "path": [ { "kind": "test" } ] }, "properties": { "propertyName": { } } } ] } }
results in this response:
400 Bad Request { "error": { "errors": [ { "domain": "global", "reason": "INVALID_ARGUMENT", "message": "Property \"propertyName\" has no value.", } ], "code": 400, "message": "Property \"propertyName\" has no value." } }
Null values work correctly in the proto API but not JSON.
http://stackoverflow.com/questions/24141010/json-structure-to-insert-a-null-value-for-a-property-into-google-cloud-datastore/24174662
The text was updated successfully, but these errors were encountered:
b/15585044
Sorry, something went wrong.
FWIW, in a listValue the API tolerates null values, but (incorrectly) ignores them. The request
{ mutation: { upsert: [ { key: key, properties: { test: { listValue: [ {}, {stringValue: 'foo'}, {}, {stringValue: 'bar'} ] } } }]} }
succeeds, but then yields the following on a subsequent lookup:
{ ... properties: { test: { listValue: [ { stringValue: 'foo' }, { stringValue: 'bar' } ] } } }
The null values have vanished.
The v1beta3 API adds an explicit null value type.
No branches or pull requests
The following request:
results in this response:
Null values work correctly in the proto API but not JSON.
http://stackoverflow.com/questions/24141010/json-structure-to-insert-a-null-value-for-a-property-into-google-cloud-datastore/24174662
The text was updated successfully, but these errors were encountered: