Skip to content

Nested equality delete: a null parent and a null leaf load the same, unlike Java #3673

Open

Description

@JeonDaehong

An equality delete on s.f loads a delete row with a null s and one with s = {f: null} the same way, as s.f IS NOT NULL (#3453). That follows the spec text ("if a parent struct column is null it implies the leaf column is null").

Java's DeleteFilter tells them apart: it compares the projected s with nullsFirst. With a probe that builds the delete set the way DeleteFilter does (StructLikeSet over selectInIdOrder, StructProjection of the data row) on iceberg 059e7ea, a delete row with a null s matches only data rows whose s is null, and s = {f: null} matches only rows with a non-null s and a null s.f.

Nothing reaches this until #2906 applies nested equality deletes on scan. Following Java would need a predicate on s itself, so the question is which one iceberg-rust should follow.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions