What steps will reproduce the problem?
1. bq load .... ---> get jobId
2. bq wait -some-job-id -some-seconds-
3. --> Unexpected exception in wait operation
What is the expected output? What do you see instead?
It should show the jobs current status and exit cleanly after the specified
wait time.
Instead of that, I get an unexpected exception and the CLI asks me to file a
bug report.
What version of the product are you using? On what operating system?
Please provide any additional information below.
Paste of output:
...
Successfully started load some-id:bqjob_r7e7fcfcfd9c87525_00000148645d42fe_1
...
[root@dmzflsrv01 logs]# bq wait
some-id:bqjob_r7e7fcfcfd9c87525_00000148645d42fe_1 5
Waiting on bqjob_r7e7fcfcfd9c87525_00000148645d42fe_1 ... (5s) 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
...
========================================
== Platform ==
CPython:2.7.5:Linux-2.6.32-220.el6.x86_64-x86_64-with-redhat-6.4-Santiago
== bq version ==
2.0.22
== Command line ==
['/mnt/data/logs/lib/google-cloud-sdk/platform/bq/bq.py', '--credential_file', '/root/.config/gcloud/legacy_credentials/eric.janz@jumbotours.com/singlestore.json', 'wait', 'jumbotour-bigquery-prod:bqjob_r7e7fcfcfd9c87525_00000148645d42fe_1', '5']
== UTC timestamp ==
2014-09-11 11:02:32
== Error trace ==
File "/mnt/data/logs/lib/google-cloud-sdk/platform/bq/bq.py", line 711, in RunSafely
return_value = self.RunWithArgs(*args, **kwds)
File "/mnt/data/logs/lib/google-cloud-sdk/platform/bq/bq.py", line 1853, in RunWithArgs
job = client.WaitJob(job_reference=job_reference, wait=secs)
File "/mnt/data/logs/lib/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
Original issue reported on code.google.com by eric.j...@jumbotours.com on 11 Sep 2014 at 11:11
Original issue reported on code.google.com by
eric.j...@jumbotours.com
on 11 Sep 2014 at 11:11