Expose jobTimeoutMs field in JobConfigurationQuery

[aravindsrinivasan]

At job creation time I want to set a timeout for the job if it takes too long to run. Too many long running queries eat up the slot reservation and significantly deteriorates query performance. Currently we have to manually cancel the queries in the console. I noticed that there is a jobTimeoutMs field in the JobConfiguration object. This is not exposed by the Python client but is exposed by other Bigquery clients (Golang). Can we add this to the Python client as well?

The alternative would be to have a timer on the client side and manually cancel the request. This feels wasteful considering the feature already exists on the server side and it's just a question of exposing it in the client.

[tswast]

This could be another good project for the apprentices.

[tswast]

Since this applies to all job configurations, this would be a good fit to add to the _JobConfig base class here:

python-bigquery/google/cloud/bigquery/job/base.py

Line 153 in 1760e94

class _JobConfig(object):

[colin-rogers-dbt]

Currently looking at how to work around this issue for users of https://github.com/dbt-labs/dbt-bigquery but solving here is definitely the ideal solution.

[lbk-fishtown]

I've started a draft PR (#1656) for this issue. I have tested the the timeout works, but I could use some guidance (pointers to docs) on what is required test wise / how to add the required tests to this.

[dataders]

@colin-rogers-dbt shipped a fix for us in dbt-labs/dbt-bigquery#902, but to reiterate, this is not the ideal place for the fix.

[dhendry]

+1 on exposing job_timeout_ms, this would be really helpful