A Google BiqQuery query is executed in almost all table queries. The table jobs were performed initially when we initially deployed our application. When the data set began to grow, we began to see Errors below. Each dataset has a huge number of tables. I am not sure if this is due to this error. However, when we run this query in a smaller dataset in another biqquery account, it succeeds.
"Error: error preparing auxiliary request: null"
Below are some examples of queries that we are trying to execute both from our application and from the Google Biq Query web console, and all our attempts have failed with the error above.
SELECT * FROM (TABLE_DATE_RANGE([sampledataset.location],
TIMESTAMP('2016-07-10'),
TIMESTAMP('2016-07-11')))
BiQ Query JOB ID reference: bquijob_286a4921_155dd7d8868
SELECT count(*) FROM (TABLE_QUERY(sampledataset,'table_id CONTAINS "location201606"'))
BiQ Query JOB ID reference: bquijob_531d0e3_155dda8f7dc
Even when I execute a table summary query, I get an error. I am not sure if this error is related.
SELECT * FROM sampledataset.__TABLES_SUMMARY__
WHERE MSEC_TO_TIMESTAMP(creation_time) <
DATE_ADD(CURRENT_TIMESTAMP(), -7, 'DAY')
Resources exceeded during query execution: Too many tables in metatable: sampledataset dataset. TABLES_SUMMARY , 500,000 limit exceeded.
Due to these problems, we believe that the Gogole Biq Query is rather unstable, and there are not enough resources to solve our problems. Before continuing with the smaller table partitions, we ran the query on stackoverflow
, bigquery?
, @jordan-tigani https://stackoverflow.com/users/1366527/jordan-tigani
- Google Biq Query AWS Redshift.
1. @Felipe Hoffa, TABLE_DATE_RANGE, Big Query, , . Big Query Google , TABLE_DATE_RANGE, " " ( , Google), . , Biq Query, TABLE_DATE_RANGE