Hi Andrew,
It might help to provide a little more detail on where you are starting
from and what you want to do once you have the data in arrow format.
If you have the data already available in some sort of off-heap
datastructure you can potentially avoid copies wrap with the existing
ArrowBuf
Hi,
Changing
> RUN python3 -c 'import pyarrow'
to
RUN LD_LIBRARY_PATH=/usr/local/lib python3 -c 'import pyarrow'
works on my environment.
Other solution:
Adding
ENV LD_LIBRARY_PATH=/usr/local/lib
before
RUN python3 -c 'import pyarrow'
Dockerfile:
...
RUN bash install_arrow.sh
Hi,
I am trying to build and install pyarrow from source in an ubuntu 18.04
docker image and getting the following error when attempting to import the
module:
Traceback (most recent call last):
> File "", line 1, in
> File
>
hi Andrew,
slightly related but probably also slightly off-topic:
(for inspiration) you may want to look at how this is done in groot/rarrow
where tools are exported to
- expose a ROOT "schema" as an Arrow Schema
- expose a ROOT Tree as an Arrow Table
groot/rarrow isn't working on zero-copy of
Hello all,
I work in particle physics, which has standardized on the ROOT (
http://root.cern) file format to store/process our data. The format itself
is quite complicated, but the relevant part here is that after
parsing/decompression, we end up with value and offset buffers holding our
data.
