Can custom dbt transformations be used to secure data within Airbyte's destination namespace? E.g. basically running transformations in transit before data hits the destination. I believe the answer is yes, I am just curious if there is existing precedent or best practices in place.

@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2626 to ensure timely resolution!

You can apply some transformations in the connector’s code; but you can’t do it for a official connector let’s say Google Ads, per example change a field value or type. dbt only apply transformation to data landed in your destination after the sync finished.

Does this mean that using dbt custom transformation leaves a small time window where untransformed data is in the destination between when it lands and when the dbt job completes?

You’re going to have the raw data and your final tables. You can run dbt after to create or edit the data the way you want. But yes, you’ll have a window with unstrasformed data

Thanks

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible. Some important considerations that will help your to get your issue solved faster: * It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem. * Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through. * Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer. * We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible. Thank you for your time and attention. Best, The Community Assistance Team