You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Java client library is missing the maximumBillingTier from the BigQuery rest API. There's no way in the SDK to set it on a per-query level for a query job configuration.
It's available in the Python SDK, but not in the Java one. We need to be able to set this at a query level - we do not want to set it project wide.
The only workaround I see to this, is rolling back to the old version of the Java libs (the old version does expose/provide it), which is obviously a massive headache for us.
The Java client library is missing the
maximumBillingTierfrom the BigQuery rest API. There's no way in the SDK to set it on a per-query level for a query job configuration.See here --> http://stackoverflow.com/questions/43647678/where-is-the-option-to-set-the-bigquery-maximum-billing-tier-in-the-new-java-sdk
And here --> https://cloud.google.com/bigquery/docs/reference/rest/v2/jobs#configuration.query.maximumBillingTier
It's available in the Python SDK, but not in the Java one. We need to be able to set this at a query level - we do not want to set it project wide.
The only workaround I see to this, is rolling back to the old version of the Java libs (the old version does expose/provide it), which is obviously a massive headache for us.