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 running dbt docs generate we are getting an error, but when using version 1.8.2 of the adapter it works like a charm.
This is the error:
Encountered an error while generating catalog: Table type cannot be None for table XXXXXXX.bronze_dev.events_mp_master_event
I can see it is happening only when trying to generate catalog in target dev, and it seems like it is affected by another source which inside it we use:
schema: "{{ 'bronze_dev' if target.name == 'dev' else 'bronze_prod' }}"
but in the source events_mp_master_event we use just:
schema: bronze_prod
so why it is affecting it?
Expected Behavior
dbt docs generate works as before
Steps To Reproduce
No response
Environment
- OS:
- Python:
- dbt:
- dbt-athena-community:
Additional Context
No response
The text was updated successfully, but these errors were encountered:
chenp-eleos
changed the title
[Bug] dbt docs generate issue in new version 1.8.3 (and 1.8.4)
[Bug] dbt docs generate issue in new version 1.8.2 (and also continues to 1.8.4)
Sep 17, 2024
Is this a new bug in dbt-athena?
Current Behavior
when running dbt docs generate we are getting an error, but when using version 1.8.2 of the adapter it works like a charm.
This is the error:
Encountered an error while generating catalog: Table type cannot be None for table XXXXXXX.bronze_dev.events_mp_master_event
I can see it is happening only when trying to generate catalog in target dev, and it seems like it is affected by another source which inside it we use:
schema: "{{ 'bronze_dev' if target.name == 'dev' else 'bronze_prod' }}"
but in the source events_mp_master_event we use just:
schema: bronze_prod
so why it is affecting it?
Expected Behavior
dbt docs generate works as before
Steps To Reproduce
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: