You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently optimize_projections rule doesn't have support for user defined nodes. When plan encounters a user defined node, currently we do not prune any field below it. However, I think we should have this support as demonstrated by your use case.
I believe this is one usecase that @berkaysynnada is planning to address via #9111
Describe the bug
Reported in DiscordL https://discord.com/channels/885562378132000778/1166447479609376850/1204466794165706802
My node requests only one column (I defined it as an expression as it stated in UserDefinedLogicalNodeCore), but parquet reader scans all the cols.
The expected behavior is:
However the actual behavior is
Projection Pushdown works with predefined nodes like filter. But not with my custom node
To Reproduce
No response
Expected behavior
No response
Additional context
This came from discord forums: https://discord.com/channels/885562378132000778/1166447479609376850/1204466794165706802
Physical Plan
The text was updated successfully, but these errors were encountered: