[jira] [Created] (ARROW-209) [C++] Broken builds: llvm.org apt repos are unavailable

2016-06-01 Thread Wes McKinney (JIRA)
Wes McKinney created ARROW-209: -- Summary: [C++] Broken builds: llvm.org apt repos are unavailable Key: ARROW-209 URL: https://issues.apache.org/jira/browse/ARROW-209 Project: Apache Arrow Issue

[jira] [Commented] (ARROW-209) [C++] Broken builds: llvm.org apt repos are unavailable

2016-06-01 Thread Wes McKinney (JIRA)
[ https://issues.apache.org/jira/browse/ARROW-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311177#comment-15311177 ] Wes McKinney commented on ARROW-209: See https://github.com/travis-ci/apt-source-whitel

Re: Question on Exactness of Arrow Memory Layout

2016-06-01 Thread Micah Kornfield
Hi Jacob, The current rough prototype/proposal of the IPC via shared memory is to do a depth first traversal of each arrays buffer and write them out to a contiguous memory block. Metadata about array types and locations of buffers is persisted at the end of memory block in flatbuffer format [1].

Question on Exactness of Arrow Memory Layout

2016-06-01 Thread Jacob Quinn
Having become familiar with the Arrow memory layout, and taking a stab at an implementation in the Julia language, I've come up with a perhaps naive question. A "type" (class) I have defined so far is: immutable Column{T} <: ArrowColumn{T} buffer::Vector{UInt8} # potential reference to mmap