Skip to content

Zone-map pruning lost on Rust-written string columns (vortex.bounded_max/bounded_min unsupported) #446

Closed

Description

@dfa1

Rust's default writer (0.86.1) records vortex.bounded_max / vortex.bounded_min instead of max/min in the vortex.zoned zone map of every Utf8/Binary column (vortex-layout/src/layouts/zoned/writer.rs, default_zoned_aggregate_fns). Both aggregates are members of core2026.08.0.

ZonedStatsSchema.aggregateStatsTableDtype cannot map them to a Stat (their state is a nested struct), so it returns null and the reader falls back to per-chunk stats. Results stay correct, but zone-map pruning is lost for every column of a Rust-written file whose zone map contains a string column.

Fix: decode the bounded aggregates' state (value + truncation flag) and use them for pruning with Rust's semantics (vortex-array/src/aggregate_fn/fns/bounded_max/). Add a filtered vortex-jni-written integration test on a string column that asserts zones are pruned.

🤖 Generated with Claude Code

Activity

  1. added
    bugSomething isn't working
    on Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions