Understanding CDC with Airbyte in GCP and the role of Orchestrator-repl-job POD


This question is about the process of Change Data Capture (CDC) using Airbyte in GCP, specifically regarding the role of the Orchestrator-repl-job POD and the flow of data from source to target.


hello . I have a question about CDC using Airbyte.

When I use CDC, the Orchestrator-repl-job POD appears, and I’m curious about what that Pod does.
Additionally, if used within GCP, is it correct that the source POD reads the WAL log using Debezium, stores it on the Pod’s disk, loads it into GCS, and the target Pod sends it from GCS to the target?

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["cdc", "airbyte", "gcp", "orchestrator-repl-job-pod", "wal-log", "debezium", "gcs"]