BigQuery Job ID Generation#618
BigQuery Job ID Generation#618jdpedrie wants to merge 1 commit intogoogleapis:bigqueryfrom jdpedrie:bigquery-job-id-generation
Conversation
|
phpunit is getting hung up on a spanner unit test:
I'm investigating now! |
|
test issue temporarily resolved by #624. |
|
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that they're okay with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
|
CLAs look good, thanks! |
This change introduces client-generated Job IDs. It also adds support for user-specified job prefixes.
The goal of this feature is to make inserting jobs idempotent. I am concerned that I may not have quite captured that in this pull request. Job IDs are generated when
BigQueryClient::runQueryAsJob()or the various Job-creating methods onTableare called. This means that multiple calls to those methods will result in different unique Job IDs, even if the configuration is identical.Those IDs are accessible after the call is executed, by invokingJob::id(). Currently there is not a means for a user to manually specify a Job ID (only a prefix); this means that one cannot retry with an existing Job ID.If this is an issue, it could be mitigated without major changes to the client by adding an optional
$jobIdargument to the various job-creating methods'$options, along with documentation advising against using it except in well-defined circumstances.