Hi Team Airbyte, I am posting this query representing the product team of Pentafox (https://pentafox.in). “We are using Airbyte extensively and replicate data from Postgres 9.6 to GBQ. We run in an ELT mode where we transform more than billion records through Airbyte every time using DBT integration across 200 schemas. We are facing a memory bloating issue when we use DBT with Airbyte as the repo in which we have the DBT code is being cloned for every single run for every connection run even if the Git repo URL is the same. It should ideally be check pointed and run only Git pull if the URL is same. Attaching two consecutive run logs for the same Repo being cloned twice for the same connection that is run twice. This is a production impact bug (as I could not find anything in docs to set any settings or purge the cloned repos after every run) and any help will really save us a lot of time.” FYI @Subramaniyaswamy Chellakumaran @Mohan Prasath

Hello Vignesh Sankaran, it's been a while without an update from us. Are you still having problems or did you find a solution?

@Marcos Marx (Airbyte) The issue still persists. We are just doing a workaround today. We can connect on a quick huddle to check it out.

Hey @Vignesh Sankaran, sorry to hear you’re still dealing with this issue. Would it be too much trouble to create a github issue surrounding this problem? I suspect it will require some more investigation in order to fix this problem.