search

sijocherian / google-bigquery

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

1 query in 7 gets generic "Unexpected Error" #154

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Query:

select count(*)
  from pricingmodel.locationproductlist lpl
    inner join pricingmodel.spdpcv pcv on( lpl.locationnumber = pcv.locationnumber and lpl.ucc = pcv.ucc )
    inner join pricingmodel.spdpzn prc on( pcv.specpricezone1 = prc.zone )
  where lpl.spcvnd = 'Y' and lpl.typecode = '2' and pcv.authdistributorflag = 'Y' and pcv.specpricezone1 in ( select specpricezone1 from pricingmodel.spdpcv  where specpricezone1 != '   ' group by specpricezone1 )

Output:

Query Failed
Error: Unexpected. Please try again.
Job ID: high-function-634:job_-Po4mvYiGNRzW2MIi9exFS4RO3k

What is the expected output? What do you see instead?
The count of records involvd

What version of the product are you using? On what operating system?
Latest - using Web UI

Please provide any additional information below.
I have modified this query in multiple ways to alleviate this issue.  None 
appear to work.  I have other queries going against the same data sets with no 
problem.  Naturally, the generic message is no help

Job id provided above

Original issue reported on code.google.com by Mendo...@gmail.com on 20 Sep 2014 at 1:11

GoogleCodeExporter commented 9 years ago 
I checked our logs, and the job ID you linked hit a transient error in the 
backend server.  The particular error has no relation to the query you ran: it 
just happened to be on a server which had a transient failure.

I do notice your query is fairly long-running, since it ran for three hours 
before hitting this issue.  Longer-running queries are more susceptible to 
transient failures of the server servicing them, which may explain why other 
queries over the same dataset succeed while this one failed.

If you have other job IDs for additional failures of this query, I'll be happy 
to look into them and see if they are also transient or if they are related to 
your query in general.

We're always working to improve the stability of BigQuery, and we hope to 
reduce the number of unexpected errors our users receive in the future.

Original comment by dk...@google.com on 20 Sep 2014 at 8:51

GoogleCodeExporter commented 9 years ago

Original comment by jcon...@google.com on 23 Jun 2015 at 4:30