There is a matrix of features missing from each language [1][2]. [1] https://arrow.apache.org/docs/status.html [2] From master (soon to be 4.0.0 release) https://github.com/apache/arrow/blob/31c8c750513f8c75a5e76a267354cb897c56468e/docs/source/status.rst
On Fri, Apr 23, 2021 at 11:51 AM Jorge Cardoso Leitão < jorgecarlei...@gmail.com> wrote: > Hi Agam, > > We have integration tests that produce data from Rust and consumes from Go, > and vice-versa, for both IPC files and streams, so it is reasonable to > expect that they work. Deviations are considered major out-of-spec bugs, > which we often prioritize over e.g. new features. > > Best, > Jorge > > > On Fri, Apr 23, 2021 at 8:45 PM Agam Brahma <agam.bra...@gmail.com> wrote: > > > Hi, > > > > Thanks for all the tips on the Go-API usage, I have the serialization > > going great there. > > > > I have a question about the compatibility of reader/writer API in > > different languages: if I have Rust services that also read/write or > > pass-through serialized arrow data, are there particular versions for > each > > language that are compatible? > > > > To be more specific, if I write out a payload of bytes using the > > ipc-writer in Go (say as the value of a json field), is it reasonable to > > expect to read that back in using the ipc-reader in Rust? (or are there > > some "known gotchas" there?) > > > > Much thanks in advance, > > Agam > > > > > > > > >
