You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Kazuaki Ishizaki (Jira)" <ji...@apache.org> on 2020/05/18 16:38:00 UTC
[jira] [Commented] (ARROW-8797) [C++] Support Flight RPC among
diffent endian platforms
[ https://issues.apache.org/jira/browse/ARROW-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110438#comment-17110438 ]
Kazuaki Ishizaki commented on ARROW-8797:
-----------------------------------------
[~apitrou] According to your comment, current FlightRPC transfers data in native endlian. In my opinion, we may have two opinions to exchange data between different endian platforms.
1. Exchange data using native endian. If the receiver detects the message endian is different from the machine-native endian, the receiver converts endian.
2. The FlightRPC always use the specific endian regardless of endian of sender or receiver.
Is there any comment?
> [C++] Support Flight RPC among diffent endian platforms
> -------------------------------------------------------
>
> Key: ARROW-8797
> URL: https://issues.apache.org/jira/browse/ARROW-8797
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, FlightRPC
> Reporter: Kazuaki Ishizaki
> Priority: Major
>
> This PR is derived from discussion in ARROW-8790. The current implementation of the Flight RPC exchanges messages using a native endlian format. It does not allow us to exchange data though Flight RPC among different endian machines (e.g. x86_64 <-> s390x).
> There is a field to show an endianness at[ https://github.com/apache/arrow/blob/master/format/Schema.fbs#L343-L346|https://github.com/apache/arrow/blob/master/format/Schema.fbs#L343-L346], which is added by ARROW-245.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)