[
https://issues.apache.org/jira/browse/ARROW-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614394#comment-17614394
]
Yaron Gvili commented on ARROW-16211:
-------------------------------------
> Only concern is about the usability. Not sure if that can be handled in this
> Jira.
Makes sense to tackle usability of the nested registry approach in a separate
jira, perhaps in the context of one of the use cases Weston listed.
> 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?
The caller would only need to pick up and query the nested registry instance at
the top of the stack. This is because each nested registry instance except the
bottom one is linked to a registry instance one step lower on the stack via a
parent link and will refer to its parent automatically.
Yes, I think it is clearer to handle the implementation of a
nested-registry-stack in one issue and any use of it (like in `CallFunction` or
`pc.call_function`) in another issue.
> [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)
