+1
-Original Message-
From: Wes McKinney
Sent: Monday, October 15, 2018 11:28 AM
To: dev@arrow.apache.org
Subject: [VOTE] Accept donation of Arrow C# .NET implementation
hi folks,
Individuals from Feyen Zylstra LLC have developed a C# implementation
of Apache Arrow and are proposing to
hings might speed up if
data is compressed (use more cpu cycles).
For in-memory format, they are typically ephemeral, and have opposite
characteristics.
On Thu, Feb 25, 2016 at 11:27 AM, Andrew Brust <
andrew.br...@bluebadgeinsights.com> wrote:
> That's extremely helpful, thank
would say that another key difference is that Parquet puts a lot of effort on
encodings and compression, and Arrow is mostly about efficient representation
to directly run operators over. eg simple arrays in memory vs bitpacked
RLE-encoded data on disk.
-Todd
On Thu, Feb 25, 2016 at 11:20 A
Is there a dumbed-down version of as summary for how and why in-mem and on-disk
formats differ? Is it mostly around aligning things for SIMD/vectorization?
There is probably some ignorance in my question, but I'm comfortable with that.
:-)
-Original Message-
From: Wes McKinney [mailto:
and thought that apps shared an allocated
memory space for the sole purpose of eliminating the need to copy data between
the apps. If it's just a replacement for protobuf SERDE, that makes it a whole
lot less exciting :(
On Wednesday, February 24, 2016 2:17 PM, Andrew Br
Hmm...that's not exactly how Jaques described things to me when he briefed me
on Arrow ahead of the announcement.
-Original Message-
From: Zhe Zhang [mailto:z...@apache.org]
Sent: Wednesday, February 24, 2016 2:08 PM
To: dev@arrow.apache.org
Subject: Re: Question about mutability
I don'
