search

sijocherian / google-bigquery

Automatically exported from code.google.com/p/google-bigquery
0 stars 0 forks source link

Unexpected internalError when importing datastore backup to Big Query. #262

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Backup and datastore entity to cloud storage
2. Try to import that backup into big query .
3.

What is the expected output? What do you see instead?
 I have a table with the content of the backup.

What version of the product are you using? On what operating system?

Please provide any additional information below.

I already imported a backup of the same entity backup a couple of days ago. 
and now i'm getting : 

Error Reason:internalError. Get more information about this error at 
Troubleshooting Errors: internalError.
Errors:
Unexpected. Please try again.
Job ID: b2btagmgr:job_uS6Ygy4AGnHP48_fe20ykjO03e0
Start Time: 6:26pm, 12 Jun 2015
End Time: 6:26pm, 12 Jun 2015
Destination Table: b2btagmgr:TagRequest.CookieActivity_20150609_2

Original issue reported on code.google.com by platf...@azalead.com on 12 Jun 2015 at 4:31

GoogleCodeExporter commented 9 years ago 
Sorry for the trouble. Working on it now!

The problem involves imports to a table with a timestamp field. One possible 
workaround is to import to an integer field and then use a query to adjust the 
schema on the imported data.

Original comment by jcon...@google.com on 12 Jun 2015 at 4:50

GoogleCodeExporter commented 9 years ago 
Thank you for answering. 

Is that a bug linked to release version of Big Query after 09/06/2015 ? 
Cuz i did the same thing that day with the same entity (same properties) and it 
worked smoothly. 
How can i import the timestamp typed "columns" to an integer ? 
Can you provide any example ? 

Thank you

Original comment by platf...@azalead.com on 12 Jun 2015 at 5:13

GoogleCodeExporter commented 9 years ago 
Yes, the regression started yesterday (2015-06-11).

Please ignore my workaround suggestion. It doesn't help, since the schema is 
inferred from the datastore backup.

We'll be rolling out a fix shortly, so hopefully the workaround will be 
unnecessary.

Original comment by jcon...@google.com on 12 Jun 2015 at 6:41

GoogleCodeExporter commented 9 years ago 
Should be fixed now. Apologies again!

Original comment by jcon...@google.com on 12 Jun 2015 at 7:38

GoogleCodeExporter commented 9 years ago 
Yes it works now . 
Thank you :)

Original comment by platf...@azalead.com on 13 Jun 2015 at 9:34