https://linen.dev logo
Join Slack
Powered by
Hi everyone. I’m still testing the system out and ...
# announcements
d
Hi everyone. I’m still testing the system out and have just came across this error during normalization: “Runtime Error in model” … “Relation name ‘xyz.abc__dbt_backup’ is longer than 63 characters” … The relation name with the __dbt_backup amended is 64 characters :(. Is this a bug, or perhaps a DBT limitation?
AH, I see on Postgres max table name length is 63 bytes.. maybe i can sort out change that config in my DB.
I was thinking for my current usecase I might have to do something custom with the transformation anyway... I was hoping to find some documentation or discussion on how to hook into the Airbyte process and replace or modify the DBT normalization step. If anyone has done this let me know
Some options to explore here it looks like - https://github.com/airbytehq/airbyte/blob/194d6cb5d07aa997fda3d7f4a937bc09173d36cf/docs/tutorials/airbyte-config-persistence.md ... exporting the normalization steps from airbyte and modifying them. looks like it will work
m
Hi @daniel fraser
hum that's a bummer... we haven't anticipated this.
were you able to work it out with DBT?
I will create a ticket so we remember to have a long term solution for it
Feel free to add more context if you think I missed smth! Thank you so much for reporting it
d
@Michel I'm spread a bit thin, will have to work on it tomorrow and see, I'm new to DBT, so will read up and update you when I sort it out. Thanks for making the tickt I will add if I have anything useful to say after dealing with it.
👍 1
m
I will ask our inhouse DBT expert (@Chris (deprecated profile) for when you come online) to see if he can unblock you
c
I am guessing DBT is working on it? https://github.com/fishtown-analytics/dbt/issues/2869
b
This is a known postgres+dbt limitation. It's because dbt creates tables with your table name + suffix for good reasons. AFAIK Fishtown actively decided to enforce it in some newer version to avoid accidental data screwups. I'd solve it by shortening the name of your table.
6 Views
Open in Slack
PreviousNext
Powered by