Hello all,

Hopefully this email works (I'm not super familiar with using mailing lists
like this).

Over the past few weeks, I've been working on a pure Julia implementation
to support serializing/deserializing the arrow format for Julia. The code
in its current state can be found here:
https://github.com/JuliaData/Arrow.jl.

I believe the code has reached an initial beta-level quality and just
finished writing the arrow <-> json integration testing code that archery
expects. I haven't worked on actual archery integration yet, but it should
just be a matter of adding a tester_julia.py file that knows how to invoke
the test/integrationtest.jl file with similar arguments as the tester_go.py
file.

This email has a couple purposes:
* Signal that the julia code is somewhat ready to be used/integrated in the
main repo
* Ask for advice/direction on actually integrating with the apache arrow
github repository

For the latter, in particular, I imagine keeping an initial PR as minimal
as possible is desirable. I need to follow up with the core pkg devs for
Julia, but I've been told it's possible/not hard to have a Julia package
"live" inside a monorepo, but I just haven't figured out the details of
what that means on the Julia General package registry side of things. But
I'm happy to figure that out and shouldn't really affect the merging of
Julia code into the apache arrow github.

So my plan is roughly:
* Fork/make a branch of the apache arrow repo
* Add in the Julia code from the link I mentioned above
* Add necessary files/integration in archery to run Julia integration tests
alongside other languages
* Do initial merge into apache arrow?

If there are other initial requirements core devs would expect, just let me
know, but I imagine that updating the implementation matrix, for example,
can be done afterwards as follow up.

Excited to have Julia more officially integrated here!

Cheers,

-Jacob
https://github.com/quinnj
https://twitter.com/quinn_jacobd

Reply via email to