spotify/luigi

Luigi is a Python module that helps you build complex pipelines of batch jobs. It handles dependency resolution, workflow management, visualization etc. It...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 12 minutes ago
Added to GitGenius on September 3rd, 2026
Created on September 20th, 2012
Open Issues & Pull Requests: 170 (+0)
GitHub issues: Enabled
Number of forks: 2,461
Total Stargazers: 18,770 (+0)
Total Subscribers: 451 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Luigi is a Python package that helps you build complex pipelines of batch jobs. It handles dependency resolution, workflow management, visualization, failure handling, and command line integration for long-running data processing tasks.

Luigi addresses the plumbing overhead of orchestrating batch processes where many tasks must be chained together, automated, and monitored through inevitable failures. Rather than replacing lower-level data processing frameworks like Hive, Pig, or Spark, Luigi stitches together tasks from diverse sources—Hadoop jobs, database operations, machine learning algorithms, Python code, or any other executable work—into coherent pipelines. It manages dependencies between tasks, tracks completion state, handles retries, and provides visualization so you can focus on defining individual tasks rather than workflow mechanics.

Luigi suits teams building data pipelines that span multiple systems and run for extended periods. It works well when you need to orchestrate heterogeneous tasks across different technologies and want built-in support for Hadoop ecosystems. The tool is particularly valuable for pipelines comprising thousands of tasks that may take days or weeks to complete. If you are choosing between Luigi and other orchestration frameworks, the README does not name direct alternatives, so comparison must come from your own evaluation of other tools in the space.

The project draws almost all of its open issues from outside users rather than the core team, indicating a substantial base of adopters running it in production. However, issues and pull requests often wait weeks or longer for a first response, suggesting limited bandwidth for maintenance and support.