alibaba/alisql

AliSQL is a MySQL branch originated from Alibaba Group. Fetch document from Release Notes at bottom.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 11th, 2026
Created on July 27th, 2016
Open Issues & Pull Requests: 15 (+0)
GitHub issues: Enabled
Number of forks: 902
Total Stargazers: 5,978 (+0)
Total Subscribers: 466 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 464.4 days
90th percentile: 2558.1 days
Tracked items: 94

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 115 days
Stale 30+ days: 12
Stale 90+ days: 10

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 (19)
  • source/upstream-mysql (4)
  • help wanted (1)
  • question (1)
  • unable to reproduce (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

AliSQL is a MySQL branch that extends the standard database with integrated analytics and vector search capabilities.

AliSQL addresses the need to perform both transactional and analytical workloads on the same data without maintaining separate systems. It accomplishes this by embedding DuckDB as a columnar storage engine alongside the traditional InnoDB engine, allowing tables to be stored and queried in either format. The tool adds native vector indexing using HNSW algorithms to support similarity search directly within the database, and includes features like temporal queries through flashback functionality and binlog optimizations for large transactions.

Teams should consider AliSQL if they run MySQL workloads that require analytical query performance without the operational complexity of separate OLTP and OLAP systems. It suits projects that need vector search integrated with relational data, or those seeking to reduce I/O overhead during large transaction commits. The tool maintains full MySQL client protocol compatibility, so existing applications and drivers work without modification. Organizations already invested in MySQL infrastructure and tooling will find the transition straightforward since AliSQL behaves as a drop-in replacement.

The project shows consistent development activity with regular updates to its core components. The maintainers actively document performance characteristics and provide benchmarking results for analytical workloads. The roadmap includes planned enhancements for DDL optimization and recovery time improvements, indicating ongoing investment in both feature breadth and operational efficiency. The codebase receives updates addressing binlog handling, transaction optimization, and vector index capabilities.