https://linen.dev logo
Join Slack
Powered by
Trying out the custom dbt transformation and wonde...
# ask-community-for-troubleshooting
g
Trying out the custom dbt transformation and wondering how the final schema is generated (
Namespace Custom Format
vs dbt project 
+schema
) e.g.
Copy code
Namespace Custom Format = "exchange_rates_api"

dbt_projects.yml
...
models:
  airbyte_dbt_exchangeratesapi:
      exchange_rates:
        +materialized: table
        +schema: exchange_rates_api
however, when running this sync. the output schema is 
airbyte_exchange_rates_api
my question is. where is the prefix 
airbyte
being created?
👀 1
✅ 1
c
what is the value of your namespace custom format? (is it 
airbyte
?)
g
Namespace Custom Format = "exchange_rates_api"
c
and so 
airbyte
is defined as your schema in your destination?
g
see the code block above in the UI i’ve set the custom format as 
exchange_rates_api
and in the dbt project i’m setting the schema as 
exchange_rates_api
and the resulting schema is 
airbyte_exchange_rates_api
c
g
yeah was thinking the same. i’ll investigate further. doing custom schemas on other projects so might be leaking over to this project
c
that’s why i am asking if your default schema in your destination is set to 
airbyte
(it will be set in your profiles.yml)
then you just need to redefine the dbt macro: 
generate_schema_name
g
yep cheers, running that custom macro now to see if it works. thanks for the prompt replies!
yeah that did it. thanks mate!
2 Views
Open in Slack
PreviousNext
Powered by