Eventual-Inc/Daft - CodSpeed

Daft

Blog Docs Changelog

Performance History

Latest Results

test(udf): drop removed execution config option

dujl:feature/udf-auto-scaling-min-max

8 hours ago

test(iceberg): read compressed files back with PyArrow

YuangGao:fix/iceberg-write-compression-codec

13 hours ago

perf(iceberg): check delete files via the manifest list instead of planning the scan

YuangGao:perf/iceberg-delete-files-from-manifest-list

14 hours ago

fix(sql): prevent overflow when parsing decimal trailing zeros

ywmoustafa8732:fix-decimal-case-coercion

2 days ago

fix(sql): support exact decimal literals in CASE expressions

ywmoustafa8732:fix-decimal-case-coercion

2 days ago

style(core): apply rustfmt to decimal inference div/mul arms The shorter bound_decimal128 arm body makes the surrounding match fully formattable, so rustfmt now breaks the `.or_else` chain and wraps the sibling Decimal128 arms that previously exceeded the width limit. This matches what CI's fmt hook produces.

hello-peter-tang:fix/7601-decimal-precision-overflow

3 days ago

style(parquet): apply cargo fmt to count-only positional-deletes test Rustfmt breaks the read_parquet(...).await.unwrap() chain (63 chars, over chain_width 60) and collapses the Int32Array::from vec literal. Fixes the failing style (fmt) CI check on #7591.

hello-peter-tang:fix/7560-count-only-positional-deletes

3 days ago

fix(core): bound decimal arithmetic precision at 38 instead of failing to plan Decimal add/sub/mul/div inference hard-errored whenever the ideal result precision exceeded 38, so ordinary chained decimal arithmetic failed to plan. This breaks TPC-H Q1 (`price * (1 - discount) * (1 + tax)`, precision 61) and Q9 (subtraction, precision 39): Cannot infer supertypes for multiply on types: Decimal[38,4], Decimal[23,2] result precision: 61 exceed bounds of [1, 38] Decimal128 is backed by an i128, so 38 digits is a hard physical limit; the ideal type simply is not representable. Instead of erroring, cap the precision at 38 and shrink the scale only as far as needed to stay valid (precision >= scale >= 0, precision >= 1) via a shared bound_decimal128 helper. This mirrors Daft's own decimal aggregation supertypes (try_sum_supertype / try_product_supertype use Decimal128(_, s) => Decimal128(38, s)) and the behaviour of Spark and DuckDB. Division also preserves the quotient's integer digits when bounding: its max(6, p1 + s2 + 1) term inflates the scale far beyond what the operands need, so keeping that scale under a 38 cap would leave zero integer digits and null out every whole-number result. Results that already fit within 38 digits are unchanged. No kernel change is required because evaluation casts both operands to the inferred output type, so the Decimal128 kernel inherits the bounded dtype. Fixes #7601

hello-peter-tang:fix/7601-decimal-precision-overflow

4 days ago

Latest Branches

0%

feat(udf): add dynamic actor pool autoscaling#7369

8 hours ago

3c4aa38

dujl:feature/udf-auto-scaling-min-max

0%

fix(iceberg): honor write.parquet.compression-codec and compression-level#7607

14 hours ago

89d06b4

YuangGao:fix/iceberg-write-compression-codec

0%

perf(iceberg): check delete files via the manifest list instead of planning the scan#7605

14 hours ago

9034343

YuangGao:perf/iceberg-delete-files-from-manifest-list

© 2026 CodSpeed Technology

Home Terms Privacy Docs