[
https://issues.apache.org/jira/browse/ARROW-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes McKinney updated ARROW-4799:
--------------------------------
Fix Version/s: (was: 0.14.0)
> [C++] Propose alternative strategy for handling Operation logical output types
> ------------------------------------------------------------------------------
>
> Key: ARROW-4799
> URL: https://issues.apache.org/jira/browse/ARROW-4799
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Priority: Major
>
> Currently in the prototype work in ARROW-4782, operations are being "boxed"
> in a strongly typed Expr types. An alternative structure would be for an
> operation to define a virtual
> {code}
> virtual std::shared_ptr<ArgType> out_type() const = 0;
> {code}
> Where {{ArgType}} is some class that encodes the arity (array vs. scalar
> vs....) and value type (if any) that is emitted by the operation.
> Operations emitting multiple pieces of data would need some kind of "tuple"
> object output. We can iterate on this
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
