[
https://issues.apache.org/jira/browse/ARROW-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613360#comment-17613360
]
Vibhatha Lakmal Abeykoon commented on ARROW-16211:
--------------------------------------------------
[~rtpsw] I think what [~jorisvandenbossche] referring to is the following
process being a management for the user.
> I believe you are referring to a burden on the user, but I don't think the
>user would actually need to do this. A normal case is when a first piece of
>code gets passed in a registry and wants to pass along a registry to a second
>piece of code. So, the first piece of code has two basic things it can do:
# Pass the registry unmodified; this keeps working in the same scope.
# Pass a nested registry wrapping it with some modifications; this creates a
nested scope.
In the regular case it is just always `pc.call_function(..)`, in this case we
have to always make sure we do `registry_x.call_function`, isn't it?
While with an approach of the ability to just drop what you don't need is way
easier. I think just a usability piece considering one use case.
May be we should also allow the ability to unregister/override functions. That
would provide flexibility for the users to use the UDFs for the said scenarios.
> [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)
