Skip to content

[DISCUSSION] Clarify public ExecutionPlan transformation contracts for optimizer-added state #23105

New issue
New issue
Closed
Closed
[DISCUSSION] Clarify public ExecutionPlan transformation contracts for optimizer-added state#23105

Description

@haohuaijin
haohuaijin
opened on Jun 23, 2026

So I suggest we discuss separately what extra contract you need for downstream usage, and then extend swap_inputs() accordingly. (and also add the above assertions to prevent similar issues)

Originally posted by @2010YOUY01 in #23078 (comment)

Activity

  1. haohuaijin
    changed the title [-][DISSCUSSION] Clarify public ExecutionPlan transformation contracts for optimizer-added state[/-] [+][DISCUSSION] Clarify public ExecutionPlan transformation contracts for optimizer-added state[/+] on Jun 23, 2026

  2. haohuaijin commented on Sep 19, 2026

    @haohuaijin
    haohuaijin
    on Sep 19, 2026
    ContributorAuthor

    do not find more contracts to discussion

  3. haohuaijin
    closed this as completedon Sep 19, 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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions