You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
Kazuaki Ishizaki / @kiszk: @pitrou 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.
Exchange data using native endian. If the receiver detects the message endian is different from the machine-native endian, the receiver converts endian.
The FlightRPC always use the specific endian regardless of endian of sender or receiver.
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, which is added by ARROW-245.
Reporter: Kazuaki Ishizaki / @kiszk
Assignee: Kazuaki Ishizaki / @kiszk
PRs and other links:
Note: This issue was originally created as ARROW-8797. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: