You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
Whenever any DBT command first runs then the following query is run to check the existence of views and tables on the entire catalog.
However, when the default catalog is large then it really hangs for a while.
Is there a way to speed this up or avoid this?
Is there a reason that it has to run over the whole catalog rather than just the relevant schema?
Thanks
WITH views AS (
select
table_catalog as database,
table_name as name,
table_schema as schema
from"awsdatacatalog".INFORMATION_SCHEMA.viewswhere table_schema =LOWER('*******')
), tables AS (
select
table_catalog as database,
table_name as name,
table_schema as schema
from"awsdatacatalog".INFORMATION_SCHEMA.tableswhere table_schema =LOWER('********')
-- Views appear in both `tables` and `views`, so excluding them from tables
EXCEPT
select*from views
)
select views.*, 'view'AS table_type FROM views
UNION ALLselect tables.*, 'table'AS table_type FROM tables
The text was updated successfully, but these errors were encountered:
Hi!
Whenever any DBT command first runs then the following query is run to check the existence of views and tables on the entire catalog.
However, when the default catalog is large then it really hangs for a while.
Is there a way to speed this up or avoid this?
Is there a reason that it has to run over the whole catalog rather than just the relevant schema?
Thanks
The text was updated successfully, but these errors were encountered: