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 have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
When generating catalog.json via dbt docs, if an Iceberg table has a column that's being dropped, the column is still shown in the catalog.json.
Iceberg tables keep track of not actual column via the property iceberg.field.current, that should be used to exclude not current columns.
Is this a new bug in dbt-athena?
Current Behavior
When generating catalog.json via dbt docs, if an Iceberg table has a column that's being dropped, the column is still shown in the catalog.json.
Iceberg tables keep track of not actual column via the property
iceberg.field.current
, that should be used to exclude not current columns.Expected Behavior
Dropped columns for iceberg tables are not shown.
Steps To Reproduce
Environment
Additional Context
https://github.com/dbt-labs/dbt-athena/pull/189/files
The text was updated successfully, but these errors were encountered: