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
At the moment, we are using nested ProjectNodes to facilitate this. The first one is the projection in the Substrait plan and the other projection is the one to select the emit fields. But this could be further optimized by just using a single ProjectNode by only using the expressions which need to be in the output.
Component(s)
C++
The text was updated successfully, but these errors were encountered:
This PR introduces an optimization to remove the additional `ProjectNode` used in handling emit feature for `ProjectRel`.
* Closes: #15096
Authored-by: vibhatha <vibhatha@gmail.com>
Signed-off-by: Weston Pace <weston.pace@gmail.com>
…15097)
This PR introduces an optimization to remove the additional `ProjectNode` used in handling emit feature for `ProjectRel`.
* Closes: apache#15096
Authored-by: vibhatha <vibhatha@gmail.com>
Signed-off-by: Weston Pace <weston.pace@gmail.com>
vibhatha
added a commit
to vibhatha/arrow
that referenced
this issue
Jan 9, 2023
…15097)
This PR introduces an optimization to remove the additional `ProjectNode` used in handling emit feature for `ProjectRel`.
* Closes: apache#15096
Authored-by: vibhatha <vibhatha@gmail.com>
Signed-off-by: Weston Pace <weston.pace@gmail.com>
Describe the enhancement requested
At the moment, we are using nested
ProjectNode
s to facilitate this. The first one is the projection in the Substrait plan and the other projection is the one to select the emit fields. But this could be further optimized by just using a singleProjectNode
by only using the expressions which need to be in the output.Component(s)
C++
The text was updated successfully, but these errors were encountered: