Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 57542200B5A for ; Thu, 4 Aug 2016 22:19:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 55DAA160AB0; Thu, 4 Aug 2016 20:19:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CCF01160AAB for ; Thu, 4 Aug 2016 22:19:21 +0200 (CEST) Received: (qmail 13426 invoked by uid 500); 4 Aug 2016 20:19:20 -0000 Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@arrow.apache.org Delivered-To: mailing list dev@arrow.apache.org Received: (qmail 13352 invoked by uid 99); 4 Aug 2016 20:19:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Aug 2016 20:19:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9B05A2C0D5E for ; Thu, 4 Aug 2016 20:19:20 +0000 (UTC) Date: Thu, 4 Aug 2016 20:19:20 +0000 (UTC) From: "Wes McKinney (JIRA)" To: dev@arrow.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARROW-245) [Format] Clarify Arrow's relationship with big endian platforms MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 04 Aug 2016 20:19:22 -0000 [ https://issues.apache.org/jira/browse/ARROW-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15408425#comment-15408425 ] Wes McKinney commented on ARROW-245: ------------------------------------ I'd be in favor of adding an endianness field to the RecordBatch flatbuffers table (default: LITTLE) https://github.com/apache/arrow/blob/master/format/Message.fbs#L140 Having a per-field endianness seems like unnecessary complexity. For now, on read we can validate that the message matches our native endianness. > [Format] Clarify Arrow's relationship with big endian platforms > --------------------------------------------------------------- > > Key: ARROW-245 > URL: https://issues.apache.org/jira/browse/ARROW-245 > Project: Apache Arrow > Issue Type: Improvement > Components: Format > Reporter: Wes McKinney > > Per August 2016 mailing list question re: big endian platforms, we have in the format document: > https://github.com/apache/arrow/blob/master/format/Layout.md#byte-order-endianness > We should clarify that this does not mean that Arrow cannot be used on big endian platforms, but rather that the canonical or "in-flight" memory representation (for IPC or memory sharing of any kind) is little-endian, so big endian systems would need to byte swap big endian integers if they intend to expose memory to any other system using Arrow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)