Skip to content

feat(table): predicate evaluation and partition-transform behavior on variant fields #1016

@laskoviymishka

Description

@laskoviymishka

Parent: #589

Tail of the Variant track. Once non-shredded support (#929 / PR #932) and shredded reader/writer (#986 / #987) land, two pieces remain:

  • Predicate binding. Predicates over a variant column need a variant_get(col, '$.path') projection at the binder so a typed predicate lowers to a column comparison the scanner can evaluate. On a shredded variant the binder should additionally use the typed-value subtree's stats for pruning.
  • Partition-spec posture. Per spec, variant fields cannot appear directly in partition specs (same posture as UnknownType). The schema visitor should reject any partition field whose source column is a variant. Future variant-aware transforms (e.g. hash over a fixed variant_get path) are not standardized yet — same parking posture as multi-arg transforms.

Stub issue so the gap has a tracker; concrete design lands once the shredded reader/writer pin the typed-value plumbing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions