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/07/25 16:02:00 UTC

[jira] [Resolved] (ARROW-5979) [FlightRPC] Expose (de)serialization of protocol types

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

Antoine Pitrou resolved ARROW-5979.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0

Issue resolved by pull request 4914
[https://github.com/apache/arrow/pull/4914]

> [FlightRPC] Expose (de)serialization of protocol types
> ------------------------------------------------------
>
>                 Key: ARROW-5979
>                 URL: https://issues.apache.org/jira/browse/ARROW-5979
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: FlightRPC
>            Reporter: lidavidm
>            Assignee: lidavidm
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> It would be nice to be able to serialize/deserialize Flight types (e.g. FlightInfo) to/from the binary representations, in order to interoperate with systems that might want to provide (say) Flight tickets or FlightInfo without using the Flight protocol. For instance, you might have a search server that exposes a REST interface and wants to provide FlightInfo objects for Flight clients, without having to listen on a separate port.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)