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?

1. https://googlecloudplatform.github.io/google-cloud-python/stable/bigquery-usage.html#querying-data-asynchronous
2. https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs