-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BigQuery: listJobs is throwing IAE #17
Comments
@shevek i tried with below example. i am not able to reproduce that error which you are getting.
Output:
|
Our code is the same. We just ran much larger volume, possibly over a larger period of time, and possibly over a number of backend revisions. Is there any way to have a job without a default dataset? We're listing jobs submitted through the GUI and potentially by other means including unit tests, I don't know how the jobs were submitted, and the ones that throw exceptions I (obviously) can't inspect to figure that out. |
@shevek without a default dataset, it will throw an error from backend. i.e. Caused by: com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad Request
{
"code" : 400,
"errors" : [ {
"domain" : "global",
"message" : "Table name \"test_list_table_a\" missing dataset while no default dataset is set in the request.",
"reason" : "invalid"
} ],
"message" : "Table name \"test_list_table_a\" missing dataset while no default dataset is set in the request.",
"status" : "INVALID_ARGUMENT"
} |
@pmakani Does this imply that it's impossible to listJobs on a job which was submitted without a default dataset? |
Closing this issue. Feel free to reopen if above reply did not help. |
Situation still arises, and the above has not helped, because when I call this function, it still throws an exception in code I do not control, but I do not appear to have permission reopen the issue. |
Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Please run down the following list and make sure you've tried the usual "quick fixes":
If you are still having issues, please be sure to include as much information as possible:
Environment details
Steps to reproduce
Happens about 100 times while listing 65,000 jobs on a project.
Code example
Stack trace
External references such as API reference guides used
Any additional information below
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
The text was updated successfully, but these errors were encountered: