search

google-code-export / google-bigquery

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

Error when listing a status of PENDING job #178

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

$ bq wait job_dsVxqvLBTrS66gAQv6z7OHEjzPU 0
Waiting on job_dsVxqvLBTrS66gAQv6z7OHEjzPU ... (0s) Current status: PENDING You 
have encountered a bug in the BigQuery CLI. Please file a bug report in our 
public issue tracker:
https://code.google.com/p/google-bigquery/issues/list
Please include a brief description of the steps that led to this issue, as well 
as the following information:

========================================
== Platform ==
  CPython:2.7.5:Darwin-13.4.0-x86_64-i386-64bit
== bq version ==
  2.0.22
== Command line ==
  ['/Users/yaniv/google-cloud-sdk/platform/bq/bq.py', '--credential_file', '/Users/yaniv/.config/gcloud/legacy_credentials/yaniv@doit-intl.com/singlestore.json', '--project', 'taboola-qa-01', 'wait', 'job_dsVxqvLBTrS66gAQv6z7OHEjzPU', '0']
== UTC timestamp ==
  2014-10-28 23:18:52
== Error trace ==
  File "/Users/yaniv/google-cloud-sdk/platform/bq/bq.py", line 714, in RunSafely
    return_value = self.RunWithArgs(*args, **kwds)
  File "/Users/yaniv/google-cloud-sdk/platform/bq/bq.py", line 1856, in RunWithArgs
    job = client.WaitJob(job_reference=job_reference, wait=secs)
  File "/Users/yaniv/google-cloud-sdk/platform/bq/bigquery_client.py", line 1784, in WaitJob
    current_status,))
========================================

Unexpected exception in wait operation: Wait timed out. Operation not finished, 
in state PENDING
What version of the product are you using? On what operating system?

OSX 10.9, latest SDK

Please provide any additional information below.

Original issue reported on code.google.com by ya...@doit-intl.com on 28 Oct 2014 at 11:21

GoogleCodeExporter commented 9 years ago 
Thanks, this is buggy reporting; the timeout from "wait" should not be 
considered unexpected and is not an internal error.

To be explicit, the "wait <job> 0" is "don't actually wait at all, just poll", 
which means the wait times out after a single poll of a pending job.

Original comment by e...@google.com on 20 Nov 2014 at 6:36