search

runt18 / google-bigquery

Automatically exported from code.google.com/p/google-bigquery
0 stars 0 forks source link

billingTierLimitExceeded appears for Load job #499

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1. Prepare 24 200MB gzip files (totally about 5GB) or more. Each line was 
formatted as JSON.
2. Call Load job API in parallel to load 24 files into a BigQuery table 
(WRITE_APPEND)
3. I got ), errors:[{:reason=>\"billingTierLimitExceeded\", :message=>\"Query 
exceeded resource limits for tier 1. Tier 2 or higher required.\"}

What is the expected output? What do you see instead?

On reading API references, `billingTierLimitExceeded` should appear only for 
query. It should not be appeared for Load job.

What version of the product are you using? On what operating system?

https://github.com/embulk/embulk-output-bigquery v0.3.0

OS: 
$ cat /etc/redhat-release
CentOS release 6.5 (Final)
$ uname -a
Linux gu2205 2.6.32-431.el6.dena.x86_64 #1 SMP Fri Aug 22 15:52:34 JST 2014 
x86_64 x86_64 x86_64 GNU/Linux

Please provide any additional information below.

job id: miIVkF2Hz5M33eLwQUIIM1nA01Q
job id: YrDAlRuz9gD259UL2qKuOFSucKQ

Original issue reported on code.google.com by seo.naot...@dena.jp on 9 Apr 2016 at 6:37

GoogleCodeExporter commented 8 years ago 
embulk-output-bigquery v0.3.0 with google-api-ruby-client v0.9.3

Original comment by seo.naot...@dena.jp on 9 Apr 2016 at 6:43

GoogleCodeExporter commented 8 years ago 
> https://cloud.google.com/bigquery/pricing#high-compute

There is no `maximumBillingTier` parameter for load job request. > 
https://cloud.google.com/bigquery/docs/reference/v2/jobs#configuration.load

Original comment by seo.naot...@dena.jp on 11 Apr 2016 at 5:57

GoogleCodeExporter commented 8 years ago 
This is a known issue that we are trying to push a fix for soon. I will provide 
another update in a few hours.

Original comment by epa...@google.com on 11 Apr 2016 at 3:17

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
We are pushing a mitigation for those two projects while we work on the fix.

Original comment by epa...@google.com on 11 Apr 2016 at 3:43

GoogleCodeExporter commented 8 years ago 
Marking as fixed for this particular project. More general update will follow 
this week.

Original comment by jcon...@google.com on 11 Apr 2016 at 5:12