apache/flink-cdc

Flink CDC is a streaming data integration tool

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 10th, 2026
Created on July 27th, 2020
Open Issues & Pull Requests: 113 (+0)
GitHub issues: Enabled
Number of forks: 2,193
Total Stargazers: 6,473 (+0)
Total Subscribers: 132 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 11.3 days
90th percentile: 11.8 days
Tracked items: 67

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 13% of issues opened in the past year have been closed. Three people close 53% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 624 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Stale (32)
  • bug (21)
  • enhancement (4)
  • blocker (2)
  • critical (1)
  • discussion (1)
  • pinned (1)
  • umbrella (1)

Detailed Description

Flink CDC is a distributed data integration tool for real-time and batch data processing built on Apache Flink.

The tool addresses the challenge of capturing and synchronizing data changes across systems in real time. It works by providing multiple API layers to accommodate different use cases: a YAML-based declarative approach for zero-code pipeline definition, and programmatic interfaces for more complex scenarios. The tool handles full database synchronization, sharding table synchronization, schema evolution, and data transformation as core capabilities, allowing users to define sources, sinks, routing rules, and transformation logic that execute on the Flink distributed runtime.

Flink CDC suits organizations that need to move data between databases and systems with minimal latency and without writing custom code. The YAML API makes it accessible to users who prefer declarative configuration, while the underlying Flink architecture supports large-scale distributed deployments. Teams managing complex data pipelines with schema changes, multi-table synchronization, or heterogeneous source and sink systems will find the built-in support for these scenarios valuable. The tool integrates with common databases and systems including MySQL, PostgreSQL, and Kafka, and can write to Paimon for data lake scenarios.

The project maintains active continuous integration with both standard and nightly test workflows. Development activity shows consistent attention to build stability and quality assurance across the codebase.