[
https://issues.apache.org/jira/browse/ARROW-16819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney updated ARROW-16819:
---------------------------------
Description: This is a design deficiency in {{CallFunction}}. If a function
is nullary (zero input arguments), the execution machinery has no way to
determine the output length from an empty vector of datums. We should add
{{CallFunction}} variants based on {{ExecBatch}} and {{ExecSpan}} (from
ARROW-16755) and figure out how to deal with the split between scalar (where
inputs must all be the same length or scalar) and vector functions (whose input
arguments can have different length) (was: This is a design deficiency in
{{CallFunction}}. If a function is nullary (zero input arguments), the
execution machinery has no way to determine the output length from an empty
vector of datums. We should change {{CallFunction}} to have variants based on
{{ExecBatch}} and {{ExecSpan}} (from ARROW-16755))
> [C++] arrow::compute::CallFunction needs a batch length for nullary functions
> -----------------------------------------------------------------------------
>
> Key: ARROW-16819
> URL: https://issues.apache.org/jira/browse/ARROW-16819
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Fix For: 9.0.0
>
>
> This is a design deficiency in {{CallFunction}}. If a function is nullary
> (zero input arguments), the execution machinery has no way to determine the
> output length from an empty vector of datums. We should add {{CallFunction}}
> variants based on {{ExecBatch}} and {{ExecSpan}} (from ARROW-16755) and
> figure out how to deal with the split between scalar (where inputs must all
> be the same length or scalar) and vector functions (whose input arguments can
> have different length)
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
