Problem you have encountered:

On 23.2.2024 we started getting errors for trying to TRUNCATE a table with rows in the streaming buffer.

googleapi: Error 400: TRUNCATE DML statement over table XXX would affect rows 
in the streaming buffer, which is not supported, invalidQuery

We have daily tests that are running for a few months now that create a table, stream rows into it and TRUNCATE it, it started failing on 23.2.2024 and never failed before.

What you expected to happen:

Expected TRUNCATE to not fail due to rows in the streaming buffer.

Steps to reproduce:

Have rows in the streaming buffer of a table and try to truncate it.

Other information (workarounds you have tried, documentation consulted, etc):

In the current documentation it seems that TRUNCATE is considered a DML statement but from previous docs it was stated that it is a DDL statement. For example here: https://cloud.google.com/blog/topics/developers-practitioners/bigquery-explained-data-manipulation-dml

This sort of change is considered a breaking change for us and we would like to understand if this is by design or a bug.

Issue 326622789

Links (7)

Issue metadata