Eventual-Inc/Daft - CodSpeed

Daft

Blog Docs Changelog

Performance History

Latest Results

style(flotilla): use `Option::unwrap_or_default` for CancellationToken clippy::unwrap-or-default fires on `self.cancel_token.unwrap_or_else(CancellationToken::new)`. `CancellationToken` already implements `Default` as a fresh independent token; switch to `unwrap_or_default()`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

colin/distributed-limit-actor

19 minutes ago

fix(json): address greptile review feedback Three review comments from greptile-apps on PR: 1. P1 json_tuple: reject duplicate field names. Calling json_tuple(expr, "a", "a") used to silently produce a Struct with two "a" fields, which caused .get("a") to return only the first match and broke serialization. We now validate uniqueness in both extract_keys_from_* paths and raise a clear ValueError at planning time. 2. P2 json_object_keys: document that key order is alphabetical. serde_json's Value::Object is backed by BTreeMap (preserve_order is not enabled), so keys come back sorted. Spark preserves insertion order. The Rust doc-comment, the SQL docstring, and the Python wrapper docstring now all explicitly call out this difference. 3. P2 json_tuple: propagate row-level nullability to the struct. Previously the result Struct was constructed with nulls=None, so every row was struct-level non-null even when the input was NULL / malformed / not an object; df["t"].is_null() always returned False on those rows. We now build a per-row validity NullBuffer and pass it to StructArray::new so is_null() correctly reflects bad inputs. Missing-key cases keep producing only field-level NULLs (the row stays valid). Tests: - New test_json_tuple_rejects_duplicate_field_names. - test_json_tuple_invalid_and_null extended to assert is_null() == True on the bad rows and to read back the struct itself. - All 17 json tests + 36 doctests pass.

XuQianJin-Stars:feat/json-functions-array-length-object-keys-tuple

1 hour ago

refactor(flotilla): simplify Distributed Limit per review Three small cleanups surfaced by a simplification-focused re-review: - Drop `LimitCounterHandle.is_done` — defined but never called from Rust or tests. `_LimitCounterImpl.is_done` stays because the unit tests use it. - Drop `DistributedLimitSinkState`. The struct carried two Arc clones that were already on the sink itself, so the state was pure boilerplate. Use `type State = ()` and clone from `&self` in `execute()` directly. Removes ~10 lines and the `make_state` ceremony. - Rewrite `start_limit_counter_actor`'s readiness wait in terms of `asyncio.wait_for` — the manual `asyncio.wait(...)` + non-empty check + `asyncio.gather` was reimplementing the same primitive. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

colin/distributed-limit-actor

3 hours ago

feat/asof-benchmarks

5 hours ago

test(dataframe): relax async-context limit assertion The distributed Limit operator now claims rows from whichever worker task finishes first, rather than strict partition order, so `limit(10)` on a 10-partition source may pull from non-consecutive partitions. The test was over-specifying which 10 values come back; what it actually cares about is that the async UDF executed in an asyncio context and produced 10 valid outputs. Assert len == 10, all odd, all in (0, 100], no duplicates instead. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

colin/distributed-limit-actor

5 hours ago

fix(flotilla): narrow has_partitioned_output to genuine amplifiers Reviewing the prior commit: MonotonicallyIncreasingId, PhysicalWrite, CommitWrite, CatalogWrite, LanceWrite, and DataSink don't need exclusion. Their tasks output rows that survive concat unchanged — the MII test failure was caused by upstream IntoPartitions, and the iceberg ADD count was lost because IntoPartitions reduced the slot count, not because writes themselves were combined. Only the genuine 1-input-to-N-outputs amplifiers (RepartitionWrite, GatherWrite, IntoPartitions, IntoBatches) need protection. Verified by re-running the previously-failing ray suite with only those four. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

colin/flotilla-coalesce-outputs

5 hours ago

refactor(flotilla): consolidate output flush to one in-loop call site Use `continue` to keep the flush check at the bottom of the loop reachable only from the buffer-add path, plus a single trailing flush after the loop. Restores the byte-bounded threshold while keeping the loop body flat. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

colin/flotilla-coalesce-outputs

6 hours ago

docs(examples): migrate text-embeddings example to public bucket (#6941) - Updates `docs/examples/text-embeddings.md` to read from `s3://daft-public-data/text-embedding-dataset.parquet` instead of `s3://desmond-demo/...`. The dataset has been copied (1.38 GB, 8 parquet parts) to the public bucket. - Renames the example's turbopuffer namespace from `desmond-scale-experiment6` to `text-embeddings-example`. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

main

7 hours ago

Latest Branches

-11%

feat(flotilla): Distributed Limit Counter#6942

44 minutes ago

f3fceaa

colin/distributed-limit-actor

-1%

feat: add JSON functions json_array_length, json_object_keys, json_tuple#6945

2 hours ago

7b1d121

XuQianJin-Stars:feat/json-functions-array-length-object-keys-tuple

0%

feat: ASOF join benchmarking scripts#6940

9 hours ago

6e2a9f6

feat/asof-benchmarks

© 2026 CodSpeed Technology

Home Terms Privacy Docs