You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Todd Farmer (Jira)" <ji...@apache.org> on 2022/07/08 21:43:00 UTC

[jira] [Updated] (ARROW-16758) [C++] Rewrite ExecuteScalarExpression to not use ScalarExecutor

     [ https://issues.apache.org/jira/browse/ARROW-16758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Farmer updated ARROW-16758:
--------------------------------
    Component/s: C++

> [C++] Rewrite ExecuteScalarExpression to not use ScalarExecutor
> ---------------------------------------------------------------
>
>                 Key: ARROW-16758
>                 URL: https://issues.apache.org/jira/browse/ARROW-16758
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Wes McKinney
>            Priority: Major
>
> {{ExecuteScalarExpression}} sets up and tears down {{ScalarExecutor}} from exec.cc for each node in the expression tree. This adds a ton of overhead from moving around non-trivial objects. After ARROW-16756, we should write a new ScalarExpressionExecutor which is careful to construct ArraySpans and execute the expression tree in a much more lightweight / less bloated fashion. 
> Follow on work in a subsequent Jira will add a pool/stack of allocated temporary buffers to reuse during execution 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)