Hi all,
Thank you all for participating in the discussion. The feedback received
was very helpful!
I have updated the spec according to the discussion here and in the PR [1]
plus the talk we had with Rok and Joris. The change in the spec can be
found in the Description of the serialization sectio
On Tue, 7 Feb 2023 at 19:32, Quentin Lhoest wrote:
>
> Hi,
>
> If I remember correctly one can already pass `types_mapper`
> to `pa.Table.to_pandas`, to allow Ray or HF Datasets to define
> their own pandas extension types associated to the arrow
> extension types. I guess this could also be used
A short update on the state of this discussion:
* There is an ongoing thread on "GH-33923: [Docs] Tensor canonical
extension type specification" [1]. Discussion is now down mostly to how
would logical layout (strides) information be encoded (if at all) and more
input would be most welcome.
* There
Hi,
If I remember correctly one can already pass `types_mapper`
to `pa.Table.to_pandas`, to allow Ray or HF Datasets to define
their own pandas extension types associated to the arrow
extension types. I guess this could also be used until there is a decision
to include those types in Arrow or not
On Thu, 2 Feb 2023 at 16:06, Clark Zinzow wrote:
>
> Hi Alenka,
>
> Great work on the RFC, I'm super excited to see this! I was planning to
> open a similar RFC at some point over the next few weeks, so this just
> saved me a bunch of work. :D
>
> At the Ray project [1], we've developed two tensor
Hi Alenka,
Great work on the RFC, I'm super excited to see this! I was planning to
open a similar RFC at some point over the next few weeks, so this just
saved me a bunch of work. :D
At the Ray project [1], we've developed two tensor extension types
(originally adapted from the tensor extension t
