Skip to content

Add check logic to validate the subquery expressions before any logical optimization rules #5463

@mingmwang

Description

@mingmwang

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
(This section helps Arrow developers understand the context and why for this feature, in addition to the what)

Some logical plans should not allow sub query exprs(Exists/InSubquery/ScalarSubquery), for example, TableScan, Values.

And for correlated subqueries, sometimes they might refer to invalid out plan's columns.
Need to add validation logic to fail the invalid plans before any logical optimization rules.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions