https://linen.dev logo
Join Slack
Powered by
Hi! I kept on getting this error even after like 3...
# ask-community-for-troubleshooting
v
Hi! I kept on getting this error even after like 3 attempts. The failures had to do with existing tables (that contain previous data). Even when I rename them, the second and third attempt also fail by pointing to another (different) tables as ambiguous.
✅ 1
2022-01-03 205655 normalization > > in macro is_incremental (macros/etc/is_incremental.sql) 2022-01-03 205655 normalization > > called by macro sqlserver__incremental_clause (macros/incremental.sql) 2022-01-03 205655 normalization > > called by macro incremental_clause (macros/incremental.sql) 2022-01-03 205655 normalization > > called by model airbyte_hubspot_deal_pipelines (models/generated/airbyte_incremental/dbo/airbyte_hubspot_deal_pipelines.sql) 2022-01-03 205655 normalization > 2022-01-03 205655 normalization > Compilation Error in model airbyte_hubspot_workflows (models/generated/airbyte_incremental/dbo/airbyte_hubspot_workflows.sql) 2022-01-03 205655 normalization > When searching for a relation, dbt found an approximate match. Instead of guessing 2022-01-03 205655 normalization > which relation to use, dbt will move on. Please delete “AirbytesDB”.“dbo”.“airbyte_hubspot_workflows”, or rename it to be less ambiguous. 2022-01-03 205655 normalization > Searched for: “airbytesDB”.“dbo”.“airbyte_hubspot_workflows” 2022-01-03 205655 normalization > Found: “AirbytesDB”.“dbo”.“airbyte_hubspot_workflows” 2022-01-03 205655 normalization > 2022-01-03 205655 normalization > > in macro is_incremental (macros/etc/is_incremental.sql) 2022-01-03 205655 normalization > > called by macro sqlserver__incremental_clause (macros/incremental.sql)
I renamed the table: airbyte_hubspot_workflows on the second attempt. I noticed the third attempt, it did not point out airbyte_hubspot_workflows table as ambigiuos but another different set of tables. Please does anyone know how I can proceed. All my tables have data already but Airbyte will fail if I ask it to sync again
c
it seems to detect a difference in capital letters on the database name too.. maybe if you lowercase things in your configurations?
v
I get but I did not create those tables manually, Airbyte did. Also, where will I get to make this lowercase configuration?
I am using MS SQL
c
oh then it seems related to @[DEPRECATED] Augustin Lafanechere experiencing: https://getdbt.slack.com/archives/CMRMDDQ9W/p1640086801132700
u
Hi, @Victor, we opened an issue for this problem here. Could you please upvote it and share your context. We suspect it's a problem on DBT's MSSQL adapter side. We need to take some time to try to reproduce.
👍 1
v
But if I may ask, is there any walk-around or stop gap to this pending when the fix will be released? This is a blocker for me right now.
c
Can you use a custom dbt transformation of the generated normalization project? That would let you edit the 
dbt_project.yml
file and disable incremental by replacing the line:
Copy code
+materialized: incremental
with:
Copy code
+materialized: table
I’m not sure if we should disable the whole incremental mode for MSSql destination while the dbt adapter requires work…? it seems like in certain scenario, it still works …
v
Thanks @Chris (deprecated profile) I still new using Airbyte. I am not sure I know how to create a custom dbt transformation yet
u
@Victor we have a guide about custom transformation here.
The idea is to retrieve our generated basic normalization model and edit them as suggested by Chris
v
oh great.. I will look into it.
I ran this to verify that the dbt project is properly configured for the workspace: 
docker run --rm -i -v airbyte_workspace:/data -w /data/106/0/normalize --network host --entrypoint /usr/local/bin/dbt airbyte/normalization debug --profiles-dir=. --project-dir=.
profiles.yml and dbt_project.yml not found… could this have been the source of the issue?
Open in Slack
PreviousNext
Powered by