> >> > >> I think we are trying to work that out now. As you've seen with some
> >> > >> of
> >> > >> you initial investigation we have no coverage for big-endian machines
> >> > yet.
> >> > >
IllegalStateException("Arrow only runs on LittleEndian systems.");
Sanjay
> From: pchan...@maprtech.com
> Date: Thu, 4 Aug 2016 17:04:34 -0700
> Subject: Re: Is there plan to support BigEndian Systems like SUN SPARC
> Hardware ?
> To: dev@arrow.apache.org; emkornfi...@gmail.com
> CC: ju
; >> Micah
> >>
> >> On Mon, Aug 1, 2016 at 11:16 AM, Sanjay Rao <getsanjay...@live.com>
> >> wrote:
> >>
> >> > Hi Wes, Hi Micah,
> >> > I understood what you meant, so point 2. Arrow working with Big Endian
> >
>
>> > Hi Wes, Hi Micah,
>> > I understood what you meant, so point 2. Arrow working with Big Endian
>> > machine to Big Endian shouldn't be an issue right ?
>> > Please confirm.
>> > Thanks,Sanjay
>> > > From: wesmck...@gmail.com
; From: wesmck...@gmail.com
> > Date: Mon, 1 Aug 2016 11:07:07 -0700
> > Subject: Re: Is there plan to support BigEndian Systems like SUN SPARC
> Hardware ?
> > To: dev@arrow.apache.org; emkornfi...@gmail.com
> >
> > hey Micah,
> >
> > On Mon, Aug 1, 201
; Subject: Re: Is there plan to support BigEndian Systems like SUN SPARC
> Hardware ?
> > To: dev@arrow.apache.org; emkornfi...@gmail.com
> >
> > hey Micah,
> >
> > On Mon, Aug 1, 2016 at 11:02 AM, Micah Kornfield <emkornfi...@gmail.com>
> wrote:
> >
Hi Wes,
The point I was trying to argue from an earlier thread is that the most
common cases for relocation are:
1. Little endian machine to little endian machine (most likely same
machine)
2. big endian machine to big endian machine (most likely same machine)
3. big endian machine to little
On Mon, Aug 1, 2016 at 10:26 AM, Wes McKinney wrote:
> hi Sanjay,
>
> You may have seen:
>
> https://github.com/apache/arrow/blob/master/format/Layout.md#byte-order-endianness
>
> For big-endian systems, they are free to work with integers with the
> native byte order, but
Sorry, please disregard my reply. I misunderstood this to be a question on
the Drill mailing list.
On Mon, Aug 1, 2016 at 9:50 AM, Parth Chandra wrote:
> Short answer is no.
> Drill's in memory format assumes little endian and it would be very
> disruptive to have to change
Short answer is no.
Drill's in memory format assumes little endian and it would be very
disruptive to have to change that.
There is a JIRA to fix the Drill client to allow little endian and we
should fix that, but it is currently low in priority.
On Mon, Aug 1, 2016 at 9:27 AM, Sanjay Rao
As Apache SPARK supports Big Endian systems.
Thanks,Sanjay
11 matches
Mail list logo