Hi ppl !! Me again. I have now airbyte in my ec2 i...
# contributing-to-airbyte
j
Hi ppl !! Me again. I have now airbyte in my ec2 instance with the source and destination successfully configured, but when i try to sync the data o reset it all fails. Here are the logs of the task if anybody knows what's going on.
u
@Juan David this seems to be a bug with our handling of names in the Postgres destination. the error is:
Copy code
[33mCompilation Error in model mundo_verde_feedback (models/generated/airbyte_tables/public/mundo_verde_feedback.sql)[0m
When searching for a relation, dbt found an approximate match. Instead of guessing 
   which relation to use, dbt will move on. Please delete "postgres"."public"."Mundo_verde_feedback", or rename it to be less ambiguous.
Searched for: "postgres"."public"."mundo_verde_feedback"
Found: "postgres"."public"."Mundo_verde_feedback"
u
to work around this, could you rename your source spreadsheet to
mundo_verde_feedback
, delete the connection (sources --> sheets — >postgres --> settings --> delete connection button) then set it up and try again?
u
@s is this bug tracked somewhere / slated for fix?
u
In the meantime I’ve created an issue to track this bug: https://github.com/airbytehq/airbyte/issues/2347
u
@s it was working all good locally in my computer, so its weird.
u
@Juan David does the proposed work around help?
u
also, to address the discrepancy between local and EC2, do they both have the same Airbyte version?
u
@s How can I check the Airbyte version ?
u
cat .env
from the EC2 instance running Airbyte
u
or you can see it in the bottom left side of the UI
u
pc VERSION=0.14.1-alpha aws VERSION=0.16.1-alpha
u
@s How can I install an specific version ?
u
if you have the git repo cloned: 1. stop airbyte (docker-compose down) 2. git pull origin master 3. docker-compose up you’ll need to delete the airbyte configurations on your local PC via
docker-compose down -v
from the repo root because 14.1 --> 16.1 contains backwards incompatible changes (but in the future you won’t need to delete any configs, we added the ability to upgrade your workspace here: https://docs.airbyte.io/tutorials/upgrading-airbyte)
u
@Juan David lmk if this helps recreate the issue locally or if you are still seeing a discrepancy