Open GoogleCodeExporter opened 9 years ago
About the 500 error:
500 errors are mostly transient and caused by internal service hiccups.
User-side caching and retry are usually sufficient ways to mitigate the
problem.
More information:
https://cloud.google.com/bigquery/streaming-data-into-bigquery#troubleshooting
>We do notice some data inconsistency, but we aren't sure to what extent our
requests are failing.
Could you please give us more details about that? What's the symptom? Any job
id(s) we can investigate?
Original comment by che...@google.com
on 2 Jan 2015 at 11:03
In regards to more information on the above note:
The symptom is we’re missing data that we know should be in there. We’ve
estimated loss around .03 - .4%, which is not ridiculous considering the size
of data we are working towards, but we’d like to keep as much data as
possible.
Does the PHP SDK automatically retry in the event of a 500??
Unfortunately I don’t have any specific Job Id’s to show. I will look into
a retry loop in the event of failed inserts.
Thank you for the quick response. :D
Original comment by e...@restorationmedia.com
on 3 Jan 2015 at 1:23
About your data loss, do you re-insert the "failed" row(s) in case of a success
response (insertErrors)?
https://cloud.google.com/bigquery/docs/reference/v2/tabledata/insertAll#response
According to the PHP SDK document
(https://developers.google.com/api-client-library/php/), I don't think it
automatically retry at 500.
Please let us know if you have more questions.
Thank you!
Original comment by che...@google.com
on 5 Jan 2015 at 8:41
Original issue reported on code.google.com by
e...@restorationmedia.com
on 2 Jan 2015 at 6:37