Skip to content

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

active 2025-03-232026-07-21 (UTC)

Partial coverage11,426 / 12,335 hourly files (93%) · 2 absent upstream · 906 failed, retryable2025-03-142026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
434
Pushes
14
Pull requests
2
Issues
29
Stars
344
Forks
18

Activity over time

Daily event counts in the loaded window

Line chart, 486 days from 2025-03-23 to 2026-07-21. Pushes: 14 total, peak 5 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 29 total, peak 16 in a day. Comments: 16 total, peak 3 in a day. Stars: 344 total, peak 46 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
baotiao24700
p1p1bear21717
kamikyo2001
JoeJRW2010
SongLibing2001
CLAassistant2002
aszenz1001
daixh3021001
changdy1000
gilbertwu1000
scott-wong1000
nandy33up1001
shawn09151001
baolinhuang1001

Recent activity

Latest issues, pull requests and releases

  • Issue#170p1p1bear2026-07-21 10:27
    Deployment Architecture Issues
  • Issue comment#155nandy33up2026-05-26 09:51
    不会又是一场声势浩大的面子工程吧?
  • Issue#154p1p1bear2026-05-26 09:41
    AliSQL 8.4.7 版本有计划开源吗
  • Issue#154gilbertwu2026-05-25 06:59
    AliSQL 8.4.7 版本有计划开源吗
  • Issue comment#148CLAassistant2026-05-12 03:05
    ci: trigger alisql-docker build on release publish
  • Issue comment#148CLAassistant2026-05-12 03:05
    ci: trigger alisql-docker build on release publish
  • Issue#144JoeJRW2026-05-11 07:57
    [Inconsistency/Bug] Vector DATA_TYPE parsing inconsistency and I_S versioning leads to MTR failures
  • Pull request#147JoeJRW2026-05-11 07:57
  • Issue comment#136p1p1bear2026-04-09 06:44
    mysqld crash at json_is_valid with release builds
  • Pull request#139p1p1bear2026-04-09 06:43
  • Issue comment#130p1p1bear2026-03-27 09:37
    Compile install failed: make[2]: *** [CMakeFiles/duckdb_proj.dir/build.make:86: extra/duckdb/build/release/stamp/duckdb_proj-build] Error 2
  • Issue#130p1p1bear2026-03-27 03:40
    Compile install failed: make[2]: *** [CMakeFiles/duckdb_proj.dir/build.make:86: extra/duckdb/build/release/stamp/duckdb_proj-build] Error 2
  • Issue#129p1p1bear2026-03-25 11:05
    mysqld crash at Dir_Walker::is_directory for debug builds
  • Issue comment#124p1p1bear2026-03-19 07:44
    Error during DuckDB node deployment
  • Issue comment#124daixh3022026-03-19 07:33
    Error during DuckDB node deployment
  • Issue comment#124p1p1bear2026-03-10 04:50
    Error during DuckDB node deployment
  • Issue#126p1p1bear2026-02-28 01:57
    关于部署AliSQL的一些疑问
  • Issue#126changdy2026-02-27 10:19
    关于部署AliSQL的一些疑问
  • Issue comment#125p1p1bear2026-02-06 03:33
    Using AliSQL with DuckDB engine as a Read-Only node for MySQL 8.0.44 upstream
  • Issue#125SongLibing2026-02-06 03:29
    Using AliSQL with DuckDB engine as a Read-Only node for MySQL 8.0.44 upstream
  • Issue comment#125SongLibing2026-02-06 03:26
    Using AliSQL with DuckDB engine as a Read-Only node for MySQL 8.0.44 upstream
  • Issue comment#123aszenz2026-02-06 01:33
    Does it work with strict mode = off?
  • Issue comment#124p1p1bear2026-02-05 06:42
    部署duckdb节点报错
  • Issue comment#124shawn09152026-02-05 06:36
    部署duckdb节点报错
  • Issue#123p1p1bear2026-02-05 06:27
    Does it work with strict mode = off?

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 344 stars here means stars gained during the window, not the repo's star count.