MySQL CDC to Parquet on S3 with Amazon MSK, Using OneFlow
Blog post from Onehouse
Onehouse OneFlow is presented as a managed change data capture service that streams MySQL inserts, updates, and deletes into Apache Parquet tables on Amazon S3, reducing the delay associated with nightly analytics loads. The setup uses MySQL binary logs in ROW format, a replication-enabled database user, a heartbeat table, an AWS Glue schema registry, and a Onehouse MySQL CDC source that provisions Amazon MSK Kafka infrastructure in the customer’s AWS account. A OneFlow managed Spark process performs an initial table copy and then syncs changes every five minutes by default, using Mutable mode to apply updates and deletes to existing rows while routing invalid records to a quarantine table. In a ticket-sales example involving 20,000 seats, the resulting Parquet table matched MySQL status counts after simulated sales activity and correctly reflected individual inserts, updates, and deletions within minutes. The tables are registered in AWS Glue and can be queried through Onehouse Lakegres, Athena, EMR, Redshift, and other compatible engines, while flow history records row-level changes for each synchronization.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Real-time | 1 | 4,128 | 1,085 | 233 | -15% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.