Why does GCDatastore backup & BQ load create RECORD with "string" and "provided" fields?
Andrey Fedorov via StackOverflow
I have half a dozen tables backing up and loading into BigQuery without any issues, but just one field on one of my models seems to translate into a RECORD field with with "string" and "provided" fields: BQ table details.
Why could this be? I'm not seeing these fields mentioned in my code in any way, nothing to indicate it in the GCD Admin Console, and the backup & load jobs are all Google's code.
Please DO NOT REPLY directly to this email but go to StackOverflow:
http://stackoverflow.com/questions/43987559/why-does-gcdatastore-backup-bq-load-create-record-with-string-and-provided
Andrey Fedorov via StackOverflow
I have half a dozen tables backing up and loading into BigQuery without any issues, but just one field on one of my models seems to translate into a RECORD field with with "string" and "provided" fields: BQ table details.
Why could this be? I'm not seeing these fields mentioned in my code in any way, and the backup & load jobs are all Google's code.
Andrey Fedorov via StackOverflow
Looks like when a string is too long to store as a ByteString in the datastore, it's automatically stored as a google.appengine.api.datastore_types.Blob, and BigQuery does not support those, so they are instead stored as
{"d_3_string": null, "d_3_provided": null}
These show up as base64encoded strings in the GCD Console.
Please DO NOT REPLY directly to this email but go to StackOverflow: