Resources exceeded during query execution in BigQuery with window function

Moderator note: Split from "Resources exceeded during query execution" when building derived table in BigQuery.

I have a situation where I’m receiving a similar error using the ROW_NUMBER() function with OVER. However in my case, I am using both a PARTITION BY and an ORDER BY. And… I’m not sure if ROW_NUMBER() with OVER() is causing the problem.
From your explanation, it sounds like ORDER BY forces BigQuery to a single node… However I’m wondering, if you use PARTITION BY along with ORDER BY, will this allow BigQuery to use more than one node?

I appreciate any insight you may have on this.
Thanks,
Stuart

0 1 528
1 REPLY 1
Top Labels in this Space