On Sun, Jan 27, 2019 at 1:08 PM Neville Dipale
wrote:
> Hi Antoine,
>
> I've given your response some thought.
>
> I'm thinking more looking at the computational aspect of Arrow. I agree
> that for representing and sharing data, RecordBatches achieve the purpose.
>
> I came across ChunkedArray,
Just to add my two cents:
The Arrow specification and Flatbuffers files defines a _binary
protocol_ for making data available at the contiguous record batch
level either in-process or via some other address space (a memory
mapped file, a socket payload / RPC message).
Chunked arrays and tables
Hi Neville,
Le 27/01/2019 à 13:07, Neville Dipale a écrit :
> Hi Antoine,
>
> I've given your response some thought.
>
> I'm thinking more looking at the computational aspect of Arrow. I agree
> that for representing and sharing data, RecordBatches achieve the purpose.
>
> I came across
Hello Neville,
I don't know if Tables need standardizing. Record Batches are part of
the spec (*), and they are the basic block for exchanging and sharing
tabular data. Depending on your application, you might exchange a
stream of Record Batches, or a fixed-length sequence thereof (in which
Hi Arrow developers,
I've been looking at the various language impls, and although a Table isn't
currently part of the spec, it seems to be implemented in CPP, Python, Go,
JS (and perhaps other languages).
Are there plans of standardising these and adding them to the spec?
I'm asking because
