Truthound · Query correctness · 3/3
Compare aggregates, joins and filters against independent expectations.
49 articles
Checking Doris COUNT plus an offset: retain the raw count and the arithmetic
A correct COUNT optimization does not automatically preserve an expression that contains COUNT.
Checking a Doris array_sort alias: ordering and element preservation are separate
Successfully registering a function does not establish that its comparator arguments retain their intended meaning.
DataFusion random-filter rewrites: similar algebra can change the sample rate
Testing one random draw against a range is different from applying two bounds to separate draws.
After adding a computed column to a DataFusion sort, recheck export order
A sort in the plan does not establish that the final exported rows remain globally ordered.
DataFusion keys after GROUP BY: validate joins at the aggregate grain
An original primary key may no longer be unique by itself after aggregation, allowing repeated contributions to disappear.
When ClickHouse shardNum shifts: validate both the range and server mapping
An integer-typed shard number does not by itself establish the provenance of distributed results.
Missing ClickHouse shards: check responding servers, not just DNS
Successful connections and queries can still read the same shard repeatedly and produce an incomplete aggregate.
ClickHouse MATERIALIZED CTEs: verify the final consumer still receives data
A successful first read does not establish that later consumers receive the same shared intermediate result.
Validating logical slice alignment in Arrow dense unions
An in-range offset can still select the wrong child value after two input windows become misaligned.
