Skip to content

Support range-key locality analysis for date_bin with a literal origin #26913

Open

Description

@benbellick

PR #26835 admits only two-argument date_bin calls. Supplying the default epoch origin explicitly produces identical bins, but three-argument calls still retain the aggregate hash shuffle even when every range split separates bins.

Audit and enable three-argument calls with a non-null literal timestamp origin, retaining the existing restrictions on timezone-less nanosecond timestamps and positive fixed-duration strides without months. The existing boundary proof should still determine locality, including rejecting crossing bins and boundary evaluation errors.

Suggested in Nga’s review comment. Related to #25344 and #25345.

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