-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
feature request: query without having to provide a jobid ? #3209
Comments
@c0b thanks for the report. AFAICT, the docs for the
|
The client library can totally solve for this by generating a job ID (e.g. |
Tracking this internally as part of GA redesign. |
i'm reading the
google-cloud-python
docs and the bigquery rest api reference [2], the job insert api is the async query job, I wonder why the python api is designed to have to provide a jobid? since bigquery server side is archiving the job id for a long time can't re-use same id, that has imposed client side a burden to maintain every jobid to be unique, although that can be easily archived by a time and random based id generator, but the point is: if the bottom layer rest api reference [2] doesn't require jobid to be provided, in the case when jobid is omitted, bigquery server will allocate a unique jobid; why the Python api becomes requiring a jobid?The text was updated successfully, but these errors were encountered: