[
https://issues.apache.org/jira/browse/ARROW-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608082#comment-17608082
]
Vibhatha Lakmal Abeykoon commented on ARROW-16211:
--------------------------------------------------
[~rtpsw] definitely this would be helpful in cleaning up things per
interpreter. I am curious about this case.
Imagine there is a UDF created in Python which does a particular job, but next
in the middle of the program we need that function to have a different behavior
(meaning another function needs to replace this function). So we expect the
same function name, but a different functionality. In such a case we still have
to remove an existing function with the same name and function signature. We
cannot check the logic of the already registered function and the new function
(in my understanding).
On top of my head what I imagine is an active interpreter, where we do a demo
of UDFs. I create a function called "func" and write some functionality. Then I
want to write another example in the same interpreter instance with the same
function name but a different functionality itself. Would this encourage
deleting the function explicitly?
Please correct me if I am wrong.
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
> 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)
