Hi all, I cloned the repo and used docker-compose to try and replicate Postgres to Snowflake. I ended up selecting all tables in my Postgres source. I tried to kill the sync and that didn’t work. I stopped the containers and deleted the images. however, if I run docker-compose again, it remembers all the tables from before, even though it cannot connect to the database (source or target). This leads me to believe that the config (data) is being persisted somewhere locally. How can I start from a clean & brand new local set-up using Docker. Thanks

hi @Zuhair Ikram you can run the following:

docker-compose down -v 
docker-compose up

and you should be up and running with a new instance of airbyte

looks like that worked. thank you @s!

I do have a follow up question. The first time, I thought that maybe I had accidentally selected all the tables in the source. however, the second time around, I made sure to only select two tables. Yet, in Snowflake, in

AIRBYTE_DATABASE.AIRBYTE_SCHEMA

I see a lot tables being created. These tables correspond to all the tables in my source. It seems like only the default structure is being created and the data is not being copied over (which is good). However, I don’t understand why

Airbyte

is creating all those tables when they aren’t being synced.

It’s annoying because even though I am only syncing two tables, I see hundreds of tables in my schema on Snowflake

By default structure, I mean the

_AIRBYTE_AB_ID

,

_AIRBYTE_DATA

and

_AIRBYTE_EMITTED_AT

columns

This sounds like a bug