hey folks, we're having a real tough time with

query is too large

errors on BQ. I believe we have the same problem described in this issue, which also has a proposed fix. Any chance we could get movement on these?

Hi Jack, apologies for the inconvenience! I left a question on the issue in order to understand your use-case a bit better. Thanks.

I left a comment in github. The short version is that we are caught between two different constraints in BQ. • without chunking the query becomes too large and complex for BQ's query planner, and it throws a resource message • with chunking the query becomes too long in terms of sheer character count, as it is invalidating the

max_query_length

So we believe we need both options to be recognized in a run to ensure our query is both short, and small, enough to run.

Same issue as me -> https://elementary-community.slack.com/archives/C02CTC89LAX/p1715262008030929

Appreciate the follow-up @Elon Gliksberg! I'm aligned with Tony here, and it sounds like aibazhang in GH has the same issue.