runt18 / google-bigquery

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

Backend Error 500 #369

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi

While testing tonight I encountered the following errors, take note that
it happens with and without a time-out set:

<HttpError 500 when requesting 
https://www.googleapis.com/bigquery/v2/projects/lucidview-playground-version1/qu
eries/job_8OCFgsW5ojBn4fwTvizIwV0zoR0?timeoutMs=20&alt=json returned "Backend 
Error">

<HttpError 500 when requesting
https://www.googleapis.com/bigquery/v2/projects/lucidview-playground-version1/qu
eries/job_4ybxElGGQBKSi6CLZ-smamVFQkw?startIndex=166&alt=json
returned "Backend Error">

The api I am using is the python api, with a service account.

Query auth details are:
SERVICE_ACCOUNT_EMAIL :
'658360963370-tfmg9a4ce0q6jnj7o4fg6vtf9o1cing9@developer.gserviceaccount.com'

PROJECT_NUMBER : '658360963370'

Dataset : andrew_test

As best as I could the error was intermittent, but cached queries did
seem to return each time, only new queries would break like this.
Regards

Original issue reported on code.google.com by andr...@lucidview.net on 12 Nov 2015 at 8:54

GoogleCodeExporter commented 8 years ago
Hello,

lucidview-playground-version1:job_8OCFgsW5ojBn4fwTvizIwV0zoR0 
lucidview-playground-version1:job_4ybxElGGQBKSi6CLZ-smamVFQkw

Both of these jobs show as DONE on the backend, with an execution time of about 
2.6 seconds.

I'll check to see if I can still get to any logs from the API serving 
infrastructure that sits between BigQuery and your client for these requests.

We are slowly migrating off of code.google.com for support.  In the future, I'd 
recommend using Stack Overflow for quicker turnaround on support requests; just 
tag your question with "google-bigquery" and one of our engineers will get back 
to you more quickly!

Original comment by thomasp...@google.com on 24 Nov 2015 at 3:24

GoogleCodeExporter commented 8 years ago
I'm sorry, we don't have the frontend logs from that date anymore.

We're (slowly) migrating off of code.google.com for support.  If you have this 
issue again, could you please post to Stack Overflow and tag your question 
"google-bigquery" ?  I apologize that our oncall missed this when you 
originally posted it here.

Original comment by thomasp...@google.com on 24 Nov 2015 at 5:57