Closed marcosmarxm closed 2 years ago
I'll try a fresh instance and see if it's reproducible.
I'd installed a clean 0.32.0-alpha version and works fine.
it would have been helpful to see what data was picked up in stargazers__dbt_tmp210240814249
(the query building that intermediate table could be found in the logs/dbt.log
file
That table could have given clues on what would be deleted and re-inserted by:
delete
from "postgres".github."stargazers"
where (_airbyte_unique_key) in (
select (_airbyte_unique_key)
from "stargazers__dbt_tmp210240814249"
);
insert into "postgres".github."stargazers" ("user", "user_id", "repository", "starred_at", "_airbyte_ab_id", "_airbyte_emitted_at", "_airbyte_normalized_at", "_airbyte_stargazers_hashid", "_airbyte_unique_key")
(
select "user", "user_id", "repository", "starred_at", "_airbyte_ab_id", "_airbyte_emitted_at", "_airbyte_normalized_at", "_airbyte_stargazers_hashid", "_airbyte_unique_key"
from "stargazers__dbt_tmp210240814249"
);
But I still don't quite understand how you would end up with empty tables...
But I still don't quite understand how you would end up with empty tables...
I am guessing, there was some "reset tables" involved in this scenario.
And so the issue boils down to the table being empty and breaking the incremental clause as discussed here https://github.com/airbytehq/airbyte/issues/8286#issuecomment-982402024
Remove this with your answer.