You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Wes McKinney (Jira)" <ji...@apache.org> on 2022/06/13 16:13:00 UTC

[jira] [Resolved] (ARROW-16819) [C++] arrow::compute::CallFunction needs a batch length for nullary functions

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

Wes McKinney resolved ARROW-16819.
----------------------------------
    Resolution: Fixed

Done in https://github.com/apache/arrow/commit/53752adc6b81166cd4ee7db5a819494042f29197

> [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)