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
I think that the problem is actually with dbt_utils package and get_column_values
macro. I tried to compile models that have that macro and they don't error, but
they just leave the compiler to run forever
After further investigation, I think that the macro causes compiler to run infinitely
if the table referenced is materialized as ephemeral
...
I found a way. to make it work now that I changed the referenced
table to be materialized as view
Steps to reproduce
I actually don't have enough context to fully know repro steps, but presumably start by trying to use the get_column_values macro on a table materialized as ephemeral.
Expected results
A table materialized as ephemeral should likely produce the same results as a table that is materialized as a view, or we should error out immediately to let users know this configuration is not valid.
Actual results
User saw an infinite spinner.
Are you interested in contributing the fix?
I could try, but I'm just on support rotation and trying to file this bug to people who have more context.
The text was updated successfully, but these errors were encountered:
After talking to @jtcohen6 it appears that dbt_utils.get_column_values is not meant to work with ephemeral models. Similar macros throw errors, and this one doesn't appear to currently! The likely fix is to throw an error when trying to use dbt_utils.get_column_values is not meant to work with ephemeral models with ephemeral models.
I don't know exactly why the infinite spinner happened (some weird product of statement + RPC + IDE?), but the short answer here is that dbt_utils.get_column_values should use the _is_ephemeral check to raise an exception if the table argument is an ephemeral model. Similar to other macros that do this today:
Describe the bug
From the user, using the Cloud IDE:
Steps to reproduce
I actually don't have enough context to fully know repro steps, but presumably start by trying to use the get_column_values macro on a table materialized as ephemeral.
Expected results
A table materialized as ephemeral should likely produce the same results as a table that is materialized as a view, or we should error out immediately to let users know this configuration is not valid.
Actual results
User saw an infinite spinner.
Are you interested in contributing the fix?
I could try, but I'm just on support rotation and trying to file this bug to people who have more context.
The text was updated successfully, but these errors were encountered: