AliSQL 8.0.44-1 — MySQL Meets DuckDB
AliSQL returns with a modern MySQL 8.0.44 codebase and native DuckDB integration, bringing high-performance analytical processing directly into the MySQL ecosystem. This stage is the DuckDB hybrid transactional and analytical processing (HTAP) debut.
The DuckDB HTAP debut
User tables can use the DuckDB storage engine, while the MySQL Data Dictionary, system tables, and other internal data remain managed by InnoDB.
Applications continue to use MySQL clients, the MySQL protocol, and SQL. Analytical queries pass through the AliSQL server layer for execution by DuckDB.
An InnoDB online transaction processing (OLTP) primary continuously synchronizes row-based binlog events to a DuckDB analytical read-only node, isolating transactional and analytical workloads.
The official 8.0.44-1 GitHub Release does not provide the detailed changelog available for 8.0.44-2. Its public commit is described as “First commit, Support DuckDB Engine.” This page therefore limits 8.0.44-1 to the DuckDB HTAP debut; native vector search, Native Flashback, Binlog in Redo V2, and Binlog Cache Free Flush belong to 8.0.44-2.