[jira] [Commented] (ARROW-16811) [C++] Remove default exec context from Expression::Bind

["Apache Arrow JIRA Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARROW-16811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615240#comment-17615240 ] 

Apache Arrow JIRA Bot commented on ARROW-16811:
-----------------------------------------------

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned per [project policy|https://arrow.apache.org/docs/dev/developers/bug_reports.html#issue-assignment]. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [C++] Remove default exec context from Expression::Bind
> -------------------------------------------------------
>
>                 Key: ARROW-16811
>                 URL: https://issues.apache.org/jira/browse/ARROW-16811
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++
>            Reporter: Weston Pace
>            Assignee: Weston Pace
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> This came up in https://github.com/apache/arrow/pull/13355.
> It is maybe not very intuitive that Expression::Bind would require an ExecContext and so we never provided one.  However, when binding expressions we need to lookup kernels, and that requires a function registry.  Defaulting to default_exec_context is something that should be done at a higher level and so we should not allow ExecContext to be omitted when calling Bind.
> Furthermore, [~rtpsw] has suggested that we might want to split Expression::Bind into two variants.  One which requires an ExecContext and one which does not (but fails if it encounters a "call").



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