How do you set up change data capture ingestion into Hudi?

CDC ingestion typically flows from a source database through a capture tool into Kafka, and then into Hudi via HoodieStreamer, so the setup spans a few distinct pieces.

1. Capture changes at the source — a tool like Debezium reads the source database's change log and publishes insert/update/delete events to Kafka topics.
2. Configure HoodieStreamer's source — point it at the Kafka topic, and select or write a schema provider (e.g., Confluent Schema Registry) matching the CDC event format.
3. Define the HoodieKey — map the source table's primary key to the record key, and choose a sensible partition path field.
4. Choose table type and payload class — MoR is the typical choice for CDC's frequent, small updates, paired with a payload class that correctly applies delete events (not just inserts/updates).
5. Run in continuous mode — so HoodieStreamer keeps consuming new events and manages its own checkpoint and table-service scheduling automatically.