Hi,
My organization already uses the official C# Arrow library for a product.
It seems that the official library is working fine on the product,
so I think it has some stability compared to what it used to be.
Moreover, I think that if we focus on the official C# implementation,
we can test it
Hi,
My organization alreadly uses the official C# Arrow library for a product.
It seems that the official library is working fine on the product,
so I think it has some stability compared to what it used to be.
Moreover, I think that if we focus on the official C# implementation,
we can test i
Wes,
>I find that people have many reasons for not contributing to
>an existing open source project, so I want to make sure I know what
>yours are, whether one of:
For the record, I have contributed to this project: both PRs and Jiras for
various 'bugs' as I found them - some (most?) made their w
On Sun, Jul 12, 2020 at 2:44 PM wrote:
>
> Wes,
>
> I thought Arrow was (or at least includes) an open standard for
> interoperability? There are even specific 'implementation guidelines'
> regarding supporting parts or all of the specification.
That's true, but at the moment there is not any C#
Hi Anthony,
On 12/07/2020 20:43, anthony.ab...@gmail.com wrote:
It appears that fragmentation is already a problem (ie private forks)
I should point out that the private fork currently used by my
organisation is a "minimal divergence" from the upstream project, and it
was my intention from th
Wes,
I thought Arrow was (or at least includes) an open standard for
interoperability? There are even specific 'implementation guidelines'
regarding supporting parts or all of the specification.
It appears that fragmentation is already a problem (ie private forks)
Where I work, we don't trust th
hi Anthony,
On Sun, Jul 12, 2020 at 12:13 PM wrote:
>
> I am in the same position as Adam - We don't use the official apache arrow
> library any more either and have been using an old fork with our own
> (probably the same) bug fixes.
>
> Personally, I have somewhat given up on the Apache .Net li
I am in the same position as Adam - We don't use the official apache arrow
library any more either and have been using an old fork with our own
(probably the same) bug fixes.
Personally, I have somewhat given up on the Apache .Net library... I have
an alternative C# arrow library that I have writt
I agree with Adam, the more usage and feedback we can get the better on the
.NET Library.
> However there is no library for C# listed anywhere else in the
> documentation.
We have some XML style doc comments in the code. It would be great if we could
generate a website/markdown from those XML
