I made a PR for this issue at https://github.com/apache/arrow/pull/5835.
Would love some more detail about what was intended by the initial issue
and what would be a better way.
On Tue, Nov 12, 2019 at 11:25 AM Joris Van den Bossche <
jorisvandenboss...@gmail.com> wrote:
> Sorry for the delay in
Sorry for the delay in response. I would suggest that you open a PR (or
point to a branch with those changes), that will make it easier to discuss
specific implementation options (rather than trying to explain and
understand it in words) and give advice.
On Wed, 6 Nov 2019 at 20:29, Justin Polchlo
Hi. I'm looking into this issue and I have some questions as someone new
to the project. The comment from Joris earlier in the thread suggests that
the solution here is to create an Array subclass for each extension type
that wants to use one. This will give a nice symmetry w.r.t. the Java
inter
That sounds about right. We're doing some work here that might require
this feature sooner than later, and if we decide to go the route that needs
this improved support, I'd be happy to make this PR. Thanks for showing
that issue. I'll be sure to tag any contribution with that ticket number.
On
On Mon, 28 Oct 2019 at 22:41, Wes McKinney wrote:
> Adding dev@
>
> I don't believe we have APIs yet for plugging in user-defined Array
> subtypes. I assume you've read
>
>
> http://arrow.apache.org/docs/python/extending_types.html#defining-extension-types-user-defined-types
>
> There may be some
Adding dev@
I don't believe we have APIs yet for plugging in user-defined Array
subtypes. I assume you've read
http://arrow.apache.org/docs/python/extending_types.html#defining-extension-types-user-defined-types
There may be some JIRA issues already about this (defining subclasses
of pa.Array wi
