Hi Antoine,
Thanks for the information, that should work for my purposes.
Regards,
Naveen
On Sat, Dec 12, 2020 at 1:49 PM Antoine Pitrou wrote:
>
> Hello Naveen,
>
> Le 12/12/2020 à 19:43, Naveen Michaud-Agrawal a écrit :
> > Is there any util code in the project (C++ or C) that can generate t
Hello Naveen,
Le 12/12/2020 à 19:43, Naveen Michaud-Agrawal a écrit :
> Is there any util code in the project (C++ or C) that can generate the
> appropriate CDataInterface struct from an Arrow buffer in the IPC format?
Not directly, but you can deserialize the IPC buffer(s) to regular Arrow
rec
Is there any util code in the project (C++ or C) that can generate the
appropriate CDataInterface struct from an Arrow buffer in the IPC format?
As a motivating use case, I would like to run the webassembly version of
DuckDb in a browser, but feed it data from an external process that can
generate
Arrow Build Report for Job nightly-2020-12-12-0
All tasks:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-12-12-0
Failed Tasks:
- centos-8-amd64:
URL:
https://github.com/ursa-labs/crossbow/branches/all?query=nightly-2020-12-12-0-github-centos-8-amd64
- debian-buster-a
Hi,
As the developer who is testing the APIs in the Arrow2ORC adapter I have a
question on whether I should necessarily take some Arrow I/O interfaces as
parameters. Are we not supposed to directly use the path of the file we write
to and directly use an ORC function to open it? If we do need t