logo

trinodb/trino

Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:Server / PlatformCategory(s):Big Data & LakehouseData Engineering & Analytics
Added to GitGenius on June 19th, 2024
Created on January 19th, 2019
Open Issues & Pull Requests: 2,717 (+2)
GitHub issues: Enabled
Number of forks: 3,817
Total Stargazers: 13,311 (+1)
Total Subscribers: 179 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 47.4 hours
Mean response time: 274.2 days
90th percentile: 1113.1 days
Tracked items: 2,449

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

56 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 7, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Roughly one issue in five opened in the past year never receives a reply. 56% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "correctness" is answered fastest, typically in about 4 hours, while "test" waits about 27 months. 59% of tracked open issues have had no activity in three months. Only 51% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2,456
New in 7 days: 11
Closed in 7 days: 22
Avg open age: 1,116 days
Stale 30+ days: 2,381
Stale 90+ days: 2,268

Recent activity

Opened in 7 days: 11
Closed in 7 days: 18
Comments in 7 days: 8
Events in 7 days: 43

Top labels

  • enhancement (884)
  • test (509)
  • good first issue (342)
  • docs (260)
  • correctness (246)
  • iceberg (216)
  • Flaky Tests (168)
  • delta-lake (141)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Trino is a distributed SQL query engine designed for fast analytics across big data systems. Written in Java, it enables users to query data from multiple sources simultaneously using standard SQL, making it a central tool for data analytics and exploration. The project was formerly known as PrestoSQL and maintains the official repository at trinodb/trino on GitHub.

The engine supports querying across diverse data sources through a connector-based architecture. The repository's topic tags indicate support for multiple data platforms including Hadoop, Hive, Delta Lake, and Iceberg, along with cloud databases and data lakes. This multi-source capability allows analysts to run unified queries across heterogeneous data environments without moving data between systems. The codebase integrates Apache Arrow for efficient data processing and supports multiple protocols for client connections, including JDBC.

Development activity on the repository shows sustained engagement from the community.

Building and developing Trino requires Java 25.0.1 or later on Mac OS X or Linux, along with Docker and Maven. The project uses a standard Maven build system, with comprehensive test suites that run through continuous integration when pull requests are submitted. The development environment supports running Trino directly in IDEs like IntelliJ IDEA, with multiple QueryRunner classes available for testing specific connectors. The codebase includes sample configurations for immediate development use and supports reproducible builds as of version 449.

The repository provides extensive documentation through its user manual and development guidelines. Contributors can reference the DEVELOPMENT.md file for code style requirements and plugin implementation guidelines, while CONTRIBUTING.md outlines contribution requirements. Security vulnerabilities can be reported through the project's security policy. The project maintains a Slack community for ongoing conversation and has published "Trino: The Definitive Guide" as a comprehensive resource for users and developers.