apache/streampark

The Open Control Plane for Real-Time Data

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 40 minutes ago
Added to GitGenius on September 16th, 2026
Created on May 27th, 2019
Open Issues & Pull Requests: 51 (+0)
GitHub issues: Enabled
Number of forks: 1,088
Total Stargazers: 4,336 (+0)
Total Subscribers: 74 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.0 days
Mean response time: 265.4 days
90th percentile: 1137.6 days
Tracked items: 412

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. Work labelled "feature/accepted" is answered fastest, typically in about 2 days, while "bug" waits about 3 weeks. 86% of issues opened in the past year have been closed, leaving a working backlog. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • bug (138)
  • feature/accepted (32)
  • good first issue (9)
  • enhancement (5)
  • feature/wip (3)
  • question (3)
  • DOCS (2)
  • FLINK (2)

Detailed Description

StreamPark is a control plane for real-time data processing that unifies management of streaming and batch workloads across Flink and Spark frameworks.

The tool addresses the operational complexity of deploying and managing data processing jobs in cloud-native environments. It provides a centralized interface for job lifecycle management, configuration, and monitoring across multiple compute engines. StreamPark abstracts away infrastructure concerns by offering Kubernetes-native deployment capabilities alongside traditional cluster support, allowing teams to define jobs declaratively and manage them through a unified control plane rather than handling each framework's deployment and operational requirements separately.

StreamPark suits organizations running production streaming pipelines with Flink or Spark that need simplified operational workflows and reduced management overhead. It is particularly valuable for teams adopting Kubernetes who want framework-agnostic job orchestration without building custom tooling. The project targets data engineering teams managing multiple concurrent jobs across different frameworks, where operational consistency and centralized visibility matter more than framework-specific optimization.

The project maintains steady development activity with regular commits addressing bug fixes, feature enhancements, and dependency updates. Pull requests receive timely review and integration. The codebase shows active maintenance of core functionality alongside incremental improvements to the user interface and operational features. Documentation receives ongoing updates to reflect changes in the tool's capabilities and deployment patterns.