You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Weston Pace (Jira)" <ji...@apache.org> on 2022/06/10 20:51:00 UTC
[jira] [Assigned] (ARROW-16811) [C++] Remove default exec context from Expression::Bind
[ https://issues.apache.org/jira/browse/ARROW-16811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weston Pace reassigned ARROW-16811:
-----------------------------------
Assignee: Weston Pace
> [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: 0.5h
> 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.7#820007)