Skip to content

Make EquivalenceProperties::new_with_schema not require aligned schema #18933

@niebayes

Description

@niebayes

There generally has requirements for renaming, appending, removing a column from the input plan.
If the input plan has an equivalence properties, it should be preserved as much as possible when the schema is altered.

However, the current EquivalenceProperties::new_with_schema implementation requires the new schema and the original schema being aligned. Specifically, the number of columns and column positions should be consistent. This constraint disallows us to consistently update the equivalence properties when the schema is altered.

I wonder if we can remove the align constraint.

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