sql - Google BigQuery: Query too large, part 2 -


can gbq team share more why "query large" error might popped? , more workarounds problem experienced: in particular, give more details of doing when popped , of resolutions never sufficed appease query-too-large gods. doing rather long comma join like

select fields a_1, a_2, ..., a_15, each had many records:

1 - 41854 2 - 32287 3 - 16876 4 - 1799 5 - 3112 6 - 6412 7 - 6424 8 - 7286 9 - 14832 10 - 17167 11 - 51149 12 - 3895 13 - 8139 14 - 38395 15 - 22858 

a_4 - a_8 1 query , needed broken or original result table result in same error. a_12 - a_15. (i did not optimize partitioning minimal number of a_i's, broke originals according date partitions coming application.)

the queries producing a_i's, i=1,...,15, pared down in terms of fields , aggregation. i.e. drawing necessary fields , aggregating as application allows (considering thoughtful, clever reductions). still popped error.

the next step aggregate away important information. worked reducing each of a_i sizes, @ expense of important view data.

i understand unioning tables might source of problem (see getting "query large" in bigquery example), if table_range or table_date_range() doing behind scenes. have table_date_range()s on dates such table_date_range()s work , table_query()s. mean comma-join doing similar has similar limitation?

insights? why popped precisely? (is language in error meaningful? code query long?) there fixes in works? much!


Comments

Popular posts from this blog

javascript - Chart.js (Radar Chart) different scaleLineColor for each scaleLine -

apache - Error with PHP mail(): Multiple or malformed newlines found in additional_header -

java - Android – MapFragment overlay button shadow, just like MyLocation button -