You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Wes McKinney <we...@gmail.com> on 2019/11/21 16:33:45 UTC
Adding stronger warnings about pre-production Arrow IPC
implementations (C#, Rust)
hi folks,
We're accruing some bug reports relating to the C# library when it
comes to interop with other languages
Nowhere in
https://github.com/apache/arrow/blob/master/csharp/README.md
is it clearly stated that such problems are to be anticipated.
Until C# participates in the integration tests as a first-class
citizen I think we should insert a highly visible warning to not build
any production applications depending on IPC-level interoperability
(unless you're prepared to roll up your sleeves and debug/fix problems
in the libraries). To be clear, it's good to have the bug reports, but
we should also set expectations appropriately.
Note that this is not stated in the Rust README either, so it is
probably a good idea to do this there, too.
- Wes
Re: Adding stronger warnings about pre-production Arrow IPC
implementations (C#, Rust)
Posted by Wes McKinney <we...@gmail.com>.
That sounds great to me.
I have just opened
https://issues.apache.org/jira/browse/ARROW-7243
On Fri, Nov 22, 2019 at 1:47 PM Uwe L. Korn <uw...@xhochy.com> wrote:
>
> Hello Wes,
>
> what about adding an implementation status (table) to the README of every language? Things like "Supports Arrow File Format", "Supports Arrow Stream Format", "Passes IPC integration tests", "Supports Flight" are things that are interesting to users and show how far an implementation has progressed.
>
> Uwe
>
> On Thu, Nov 21, 2019, at 5:33 PM, Wes McKinney wrote:
> > hi folks,
> >
> > We're accruing some bug reports relating to the C# library when it
> > comes to interop with other languages
> >
> > Nowhere in
> >
> > https://github.com/apache/arrow/blob/master/csharp/README.md
> >
> > is it clearly stated that such problems are to be anticipated.
> >
> > Until C# participates in the integration tests as a first-class
> > citizen I think we should insert a highly visible warning to not build
> > any production applications depending on IPC-level interoperability
> > (unless you're prepared to roll up your sleeves and debug/fix problems
> > in the libraries). To be clear, it's good to have the bug reports, but
> > we should also set expectations appropriately.
> >
> > Note that this is not stated in the Rust README either, so it is
> > probably a good idea to do this there, too.
> >
> > - Wes
> >
Re: Adding stronger warnings about pre-production Arrow IPC implementations (C#, Rust)
Posted by "Uwe L. Korn" <uw...@xhochy.com>.
Hello Wes,
what about adding an implementation status (table) to the README of every language? Things like "Supports Arrow File Format", "Supports Arrow Stream Format", "Passes IPC integration tests", "Supports Flight" are things that are interesting to users and show how far an implementation has progressed.
Uwe
On Thu, Nov 21, 2019, at 5:33 PM, Wes McKinney wrote:
> hi folks,
>
> We're accruing some bug reports relating to the C# library when it
> comes to interop with other languages
>
> Nowhere in
>
> https://github.com/apache/arrow/blob/master/csharp/README.md
>
> is it clearly stated that such problems are to be anticipated.
>
> Until C# participates in the integration tests as a first-class
> citizen I think we should insert a highly visible warning to not build
> any production applications depending on IPC-level interoperability
> (unless you're prepared to roll up your sleeves and debug/fix problems
> in the libraries). To be clear, it's good to have the bug reports, but
> we should also set expectations appropriately.
>
> Note that this is not stated in the Rust README either, so it is
> probably a good idea to do this there, too.
>
> - Wes
>