dtstack/chunjun

A data integration framework

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on April 3rd, 2018
Open Issues & Pull Requests: 287 (+0)
GitHub issues: Enabled
Number of forks: 1,683
Total Stargazers: 4,102 (+0)
Total Subscribers: 162 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 75.1 days
Mean response time: 280.0 days
90th percentile: 693.0 days
Tracked items: 54

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Work labelled "question" is answered fastest, typically in about 3 days, while "bug" waits about 10 months. Three people close 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 983 days
Stale 30+ days: 11
Stale 90+ days: 11

Recent activity

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

Top labels

  • bug (21)
  • question (18)
  • feature-request (13)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Chunjun is a data integration framework built on Apache Flink that enables batch and stream processing of data across diverse sources and destinations.

The framework addresses the challenge of moving and transforming data between heterogeneous systems by providing a unified platform that abstracts away the complexity of different data connectors. Rather than requiring developers to write custom Flink jobs for each integration scenario, Chunjun offers pre-built connectors and a declarative approach to defining data pipelines. It supports both batch and streaming modes, allowing teams to handle real-time data synchronization as well as bulk data migration tasks through a single framework.

Chunjun suits organizations that need to integrate data across multiple systems without building custom Flink applications for each scenario. It is particularly valuable for teams already invested in the Flink ecosystem who want to reduce development time for data pipeline creation. The framework is appropriate for enterprises managing complex data landscapes where connectivity to numerous databases, data warehouses, and message queues is required. Teams should consider Chunjun if they prioritize operational simplicity and want to leverage Flink's distributed processing capabilities without writing extensive boilerplate code.

The project shows sustained development activity with regular commits addressing bug fixes and feature enhancements. Pull requests are reviewed and merged consistently, indicating an active maintenance cycle. The codebase receives updates that extend connector support and improve core framework stability. Issue tracking demonstrates responsiveness to user-reported problems and feature requests. Documentation is maintained alongside code changes to reflect framework evolution.