[jira] [Commented] (ARROW-4799) [C++] Propose alternative strategy for handling Operation logical output types

["Antoine Pitrou (Jira)" <ji...@apache.org>]

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

Antoine Pitrou commented on ARROW-4799:
---------------------------------------

Is this still relevant? It seems like the expression layer from datasets should be used instead.
cc [~fsaintjacques]

> [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
(v8.3.4#803005)