Skip to content

Support Substrait exchange output for range repartitioning #22788

Open

Description

@gene-bordegaray

Will Update With More Depth

Part of #22395.

Substrait exchange production currently rejects LogicalPlan::Repartition with Partitioning::Range.

Add Substrait exchange support for logical range repartitioning once the appropriate Substrait representation or extension mapping is decided.

Activity

  1. saadtajwar commented on Jun 20, 2026

    @saadtajwar
    Contributor

    Hey @gene-bordegaray ! Took a cursory look through this and the Substrait docs - it looks like this Range repartitioning isn't currently supported by the existing Substrait exchange types - is the recommended approach here to use the "advanced extension" field to create our own Datafusion-specific serialization, or propose an addition upstream to Substrait itself? Happy to help in either case!

  2. Rich-T-kid commented on Jul 18, 2026

    @Rich-T-kid
    Contributor

    Hey @gene-bordegaray ! Took a cursory look through this and the Substrait docs - it looks like this Range repartitioning isn't currently supported by the existing Substrait exchange types - is the recommended approach here to use the "advanced extension" field to create our own Datafusion-specific serialization, or propose an addition upstream to Substrait itself? Happy to help in either case!

    any update on this? @saadtajwar

  3. saadtajwar commented on Jul 20, 2026

    @saadtajwar
    Contributor

    Hey @gene-bordegaray ! Took a cursory look through this and the Substrait docs - it looks like this Range repartitioning isn't currently supported by the existing Substrait exchange types - is the recommended approach here to use the "advanced extension" field to create our own Datafusion-specific serialization, or propose an addition upstream to Substrait itself? Happy to help in either case!

    any update on this? @saadtajwar

    Hey @Rich-T-kid - sorry I haven't had a chance to follow back up on this - I'm happy to do a quick look into the process for supporting a new Substrait exchange type vs using the advanced extensions if that would be helpful for us to decide the path forward here!

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