[
https://issues.apache.org/jira/browse/ARROW-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614337#comment-17614337
]
Vibhatha Lakmal Abeykoon commented on ARROW-16211:
--------------------------------------------------
I am also not against the safety features discussed. +1 on that.
Only concern is about the usability. Not sure if that can be handled in this
Jira.
I like the idea about an API to make use the nested registries as a stack and
make a caller which scans through the registries and finding the function being
called. Should we create a separate ticket for this?
Regarding the usecases,
Probably the second use case can be added to this JIRA. But the third case
seems to be a separate ticket.
cc [~westonpace]
> [C++][Python] Unregister compute functions
> ------------------------------------------
>
> Key: ARROW-16211
> URL: https://issues.apache.org/jira/browse/ARROW-16211
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: C++, Python
> Reporter: Vibhatha Lakmal Abeykoon
> Assignee: Vibhatha Lakmal Abeykoon
> Priority: Major
>
> In general, when using UDFs, the user defines a function expecting a
> particular outcome. When building the program, there needs to be a way to
> update existing function kernels if it expands beyond what is planned before.
> In such situations, there should be a way to remove the existing definition
> and add a new definition. To enable this, the unregister functionality has to
> be included.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
