If you do a `create or replace table ...` when the quota has already been exceeded then as expected the table doesn't change (this i have double checked), however...
If you are running multiple queries concurrently (e.g. via dbt), and one of the queries exhausts the quota it seems that it's possible that any concurrent `create or replace table ...` queries can fail, but rather than simply abort safely, they can end up deleting the old version of the table that they were set to replace.
I have not attempted to reproduce this race condition, but right now that seems the most likely issue with what we have observed.
Has anyone else seen this? We've only noticed it as of today (2024-Nov-12), so wonder if it is a new bug.
Thanks
LinkedIn
Twitter
