简体   繁体   English

更改 BigQuery API 的 maximumBillingTier?

[英]Change maximumBillingTier for BigQuery API?

I'm currently running a query that requires billing tier 4. When running my post request to the query endpoint, I'm setting "maximumBillingTier":4 .我目前正在运行一个需要计费层 4 的查询。在向查询端点运行我的发布请求时,我正在设置"maximumBillingTier":4 I'm able to run the query successfully within the BigQuery console but not from my actual application with the API.我能够在 BigQuery 控制台中成功运行查询,但不能从我使用 API 的实际应用程序中成功运行。 My projects default billing tier is Tier 1.我的项目默认计费层是第 1 层。

if there is a way to change the billing tier for my project如果有办法更改我的项目的计费层

You can submit the BigQuery High-Compute queries form to set a project-wide default您可以提交 BigQuery 高计算查询表单以设置项目范围的默认值

Update:更新:

As per November 14, 2017 Release Notes -根据November 14, 2017 Release Notes -

High compute queries are being phased out so you are no longer required to opt-in.高计算查询正在逐步淘汰,因此您不再需要选择加入。 All high compute queries under tier 100 are billed as tier 1. Running a high compute query does not require setting a threshold flag.第 100 层下的所有高计算查询都按第 1 层计费。运行高计算查询不需要设置阈值标志。

All queries above tier 100 will fail with a RESOURCES_EXCEEDED_PER_BYTE error unless the query is running in a reserved instance.除非查询在保留实例中运行,否则第 100 层以上的所有查询都将失败并显示 RESOURCES_EXCEEDED_PER_BYTE 错误。 Existing users who have run a high compute query higher than tier 100 in the last 30 days retain the ability to run queries at the higher billing tier until October 31, 2018.在过去 30 天内运行高于第 100 层的高计算查询的现有用户保留在更高计费层运行查询的能力,直到 2018 年 10 月 31 日。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM