when rebuilding tables, dbt should use table renaming to minimize amount of time the table is unavailable

[jthandy]

rather than dropping the table and then rebuilding it from a query, it would be better to create a new table with a temporary name, wait for the query to finish, then drop the old table, then rename the new table to the correct name. this would result in a significantly smaller window in which the table was unavailable for querying.

[doncorrea-vroom]

Was this enhancement request ever addressed? We're encountering issues with timing of our dbt model runs coinciding with looker queries or scheduled reports which ultimately errors out with "table does not exist". Using v 0.16.1

[drewbanin]

hey @doncorrea-vroom - can you create a new issue if you're having an issue with dbt v0.16.1? Thanks!