You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Antoine Pitrou (JIRA)" <ji...@apache.org> on 2019/06/04 14:44:00 UTC

[jira] [Commented] (ARROW-5331) [C++] FlightDataStream should be higher-level

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

Antoine Pitrou commented on ARROW-5331:
---------------------------------------

I had overlooked that the {{FlightDescriptor}} is unused where {{FlightDataStream}} is concerned. {{FlightDataStream}} is used for the server's {{DoGet}} implementation only. So {{RecordBatchStream}} should already be sufficient in all cases where a record batches-only data stream is desired.

This leaves the question of heterogenous Flight streams. They should be handled at the IPC layer first before adapting Flight to work with them. We probably need some kind of IPC {{Datum}} that can represent several different kinds of data (record batch, tensor...).

> [C++] FlightDataStream should be higher-level
> ---------------------------------------------
>
>                 Key: ARROW-5331
>                 URL: https://issues.apache.org/jira/browse/ARROW-5331
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: C++, FlightRPC
>    Affects Versions: 0.13.0
>            Reporter: Antoine Pitrou
>            Priority: Major
>
> Currently, {{FlightDataStream}} is expected to provide {{FlightPayload}} objects. This requires the user to handle IPC serialization themselves.
> Instead, it could provide higher-level {{FlightData}} objects (perhaps a simple struct containing a {{FlightDescriptor}} and a {{RecordBatch}}), letting Flight handle IPC encoding.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)