search

runt18 / google-bigquery

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

TABLE_DATE_RANGE assumes wrong table's amount with monthly tables #461

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Store tables named with dates at the end. For example, a range starting 
20120101 to 20160101
2. Use the TABLE_DATE_RANGE to query those tables

What is the expected output? What do you see instead?
I expected to get results from the query, but instead i get an error message 
saying:
"Error: TABLE_DATE_RANGE error: too many days"

What version of the product are you using? On what operating system?
BigQuery Web UI and the google-api-python-client==1.4.2

Wrongly, I asked a question here, trying to open an issue: 
http://stackoverflow.com/questions/35807769/table-date-range-assumes-wrong-table
s-amount-with-monthly-tables

I attached a screenshot showing the message.

Hope you guys can fix this soon :)

Original issue reported on code.google.com by wesley.b...@easytaxi.com on 4 Mar 2016 at 11:39

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks, we're looking into the possibility of making this change.  How many 
years worth of months would you need?

Original comment by e...@google.com on 5 Mar 2016 at 1:08

GoogleCodeExporter commented 8 years ago 
On this specific use case we need less then 4 years, but this will increase as 
the time goes.

What seems to make more sense here, for me, it is to get the tables and count 
them given the date range on the TABLE_DATE_RANGE. What do you think?

Original comment by wesley.b...@easytaxi.com on 7 Mar 2016 at 1:05

GoogleCodeExporter commented 8 years ago 
I need this as well. I agree that counting the tables, rather than assuming 
they all exist, is a correct solution.

Original comment by chr...@wepay.com on 10 Mar 2016 at 6:49

GoogleCodeExporter commented 8 years ago 
Increased to a 10-year date range.  The limit of 1000 actual tables per query 
still applies, so this increase is only really helpful for tables that don't 
exist for every day.

Does your query work now?

Original comment by e...@google.com on 29 Mar 2016 at 5:13