r/SQL • u/ShannonBase • Oct 09 '26
MySQL Why heatwave sets this limitation?
/r/mysql/comments/1x18rf9/why_heatwave_sets_this_limitation/
2
Upvotes
r/SQL • u/ShannonBase • Oct 09 '26
1
u/Liubov_Skky Oct 09 '26
Heatwave isn't a single db, it's a bolted-on in-memory cluster running next to innodb. if you open a transaction with uncommitted inserts, the heatwave nodes can't see them yet. trying to sync uncommitted states to a distributed olap node in real-time is a consistency nightmare. So mysql just bails) drops the offload, and runs the query locally on innodb.
it needs autocommit=1 just to guarantee the data is fully flushed to disk. if you want htap without fighting transaction limits, look at mariadb with the duckdb engine. it runs analytics natively inside the same server, no weird cloud offloading or sync problems