Effect of changing table clustering in BigQuery on Airbyte queries


When changing the table clustering in BigQuery, it can impact the cost and performance of Airbyte queries. Understanding the implications of clustering columns like the primary key and _airbyte_emitted_at is crucial.


Hello, hI have the following question.
I recently upgrade the destinations to to destination V2. Now, in BigQuery, I saw that the tables are clustered by the primary key and _airbyte_emitted_at . I assume that those columns helps to reduce the cost in the “merge” process, is that true?

I am asking because I want to cluster that table by a new column to reduce cost when I query that table. If I change the table cluster config, that. would affect the process right? Making the Airbyte’s queries more expensive?

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["bigquery", "table-clustering", "airbyte-queries", "cost-reduction"]