Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optimize plans involving table functions #16012

Merged
merged 9 commits into from
Mar 30, 2023

Conversation

kasiafi
Copy link
Member

@kasiafi kasiafi commented Feb 7, 2023

This PR introduces optimizer rules for column pruning and redundant node pruning of TableFunctionProcessorNode.

Docs not needed.

Release notes

( ) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
(X) Release notes are required, with the following suggested text:

# General
* Optimize queries involving table functions with table arguments.

@losipiuk
Copy link
Member

Prune unreferenced pass-through columns of table function LGTM

@losipiuk
Copy link
Member

Prune unreferenced columns of table function source LGTM

kasiafi added 9 commits March 29, 2023 16:05
Add more detailed check for TableFunctionProcessorNode.passThroughSpecifications
in TableFunctionProcessorMatcher.
Add check for TableFunctionProcessorNode.requiredSymbols
in TableFunctionProcessorMatcher.
Add check for TableFunctionProcessorNode.hashSymbol
in TableFunctionProcessorMatcher.
Adds an optimizer rule to remove TableFunctionProcessorNode with
source being an empty relation, based on the "prune when empty"
property.
@kasiafi kasiafi force-pushed the 453TestTFPruningInPlans branch from d0b3b58 to 0d8fe19 Compare March 29, 2023 14:19
@kasiafi
Copy link
Member Author

kasiafi commented Mar 29, 2023

Applied comments.

@kasiafi kasiafi merged commit e2aab1e into trinodb:master Mar 30, 2023
@github-actions github-actions bot added this to the 412 milestone Mar 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants