v1.0.2
Release date: May 14, 2026
This release fixes a bug where a query could return incorrect rows when all of the following were true:
- the table uses merge mode (
merge_mode); - the range result cache is enabled;
- the query filters the time index column with
OR(e.g.WHERE ts = a OR ts = b).
In this case the cache could reuse a previous query's result and return rows that should have been filtered out. This is now fixed. We recommend users on v1.0.0 and v1.0.1 upgrade to v1.0.2. (#8105)
🚀 Features
🐛 Bug Fixes
- fix: window sort off by one precision TimeRange&better alias track by @discord9 in #8019
- fix(server): describe EXPLAIN statements so bind parameters work by @BootstrapperSBL in #8035
- fix: windows windowed sort ci by @discord9 in #8039
- fix: batched prometheus ingest row metric by @v0y4g3r in #8054
- fix: preserve case in database name from connection string by @v0y4g3r in #8062
- fix(metric-engine): validate column types and require time index in verify_rows by @BootstrapperSBL in #8018
- fix: type inference for sql rewrite by @sunng87 in #8052
- fix: infer time index from column meta on derived table by @waynexia in #8013
- fix(mito): ignore compaction override in enum option validation by @QuakeWang in #8094
- fix(mito2): drop unsound time-filter cache-key stripping by @evenyag in #8105
- fix: remap batch table route addresses by @WenyXu in #8109
- fix: avoid stale route update during repartition allocation by @WenyXu in #8115
New Contributors
- @BootstrapperSBL made their first contribution in #8018
All Contributors
We would like to thank the following contributors from the GreptimeDB community:
@BootstrapperSBL, @QuakeWang, @WenyXu, @discord9, @evenyag, @sunng87, @v0y4g3r, @waynexia