ang Wu wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > On Fri, Sep 6, 2024 at 3:57 AM Sutou Kouhei
> > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > In <
> > cah4123zv0ph37hrufui
>
> > > +1 (binding)
> > >
> > > In >
> > > "[VOTE] Allow Decimal32 and Decimal64 bitwidths in Arrow Format" on
> Wed,
> > > 4 Sep 2024 17:17:49 -0400,
> > > Matt Topol wrote:
> > >
> > > > Based on variou
+1 (binding)
On Fri, 6 Sept 2024 at 03:57, Gang Wu wrote:
>
> +1 (non-binding)
>
> On Fri, Sep 6, 2024 at 3:57 AM Sutou Kouhei wrote:
>
> > +1 (binding)
> >
> > In
> > "[VOTE] Allow Decimal32 and Decimal64 bitwidths in Arrow Format" on Wed
+1 (binding)
In
"[VOTE] Allow Decimal32 and Decimal64 bitwidths in Arrow Format" on Wed, 4
Sep 2024 17:17:49 -0400,
Matt Topol wrote:
> Based on various discussions among the ecosystem and to continue expanding
> the zero-copy interoperability for Arrow to be use
+1 (binding).
Can you open a PR with the spec updates?
Regards
Antoine.
Le 04/09/2024 à 23:17, Matt Topol a écrit :
Based on various discussions among the ecosystem and to continue expanding
the zero-copy interoperability for Arrow to be used with different
libraries and databases (such as
@Micah, I mostly started the vote now because I've spent the last week and
a half in C++ template hell + playing wack-a-mole with unit tests and
wanted to have something to show for it while I put the finishing cleanup
on the Go implementation. The other reason is pretty much for the reason
that Fe
+1 (non-binding)
Micah Kornfield, you have a good point. One spec without at least 2
implementations is not a serious spec.
But I think we can run the vote now and defer the merging of the
implementations until we are confident both implementations are almost
complete, tested and the spec text co
+1 (non-binding)
I can upload a PR for the corresponding C# change within the next day.
On Wed, Sep 4, 2024 at 2:21 PM Matt Topol wrote:
> Based on various discussions among the ecosystem and to continue expanding
> the zero-copy interoperability for Arrow to be used with different
> libraries
Based on various discussions among the ecosystem and to continue expanding
the zero-copy interoperability for Arrow to be used with different
libraries and databases (such as libcudf, ClickHouse, etc) I would like to
propose that we extend the allowable bit-widths for Arrow Decimal types to
allow 3
