[
https://issues.apache.org/jira/browse/HIVE-14074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344618#comment-15344618
]
Sergio Peña commented on HIVE-14074:
------------------------------------
[~ayousufi] is this thread-safe? I see that
{{FunctionRegistry.unregisterPermanentFunctions(}} has a lock/unlock block
while the functions are deleted, but what would happen while functions are
added back? During the time where functions are added, then we do not have any
function on the DB, will other users have issues with queries that use
functions that were deleted for a short period of time?
> RELOAD FUNCTION should update dropped functions
> -----------------------------------------------
>
> Key: HIVE-14074
> URL: https://issues.apache.org/jira/browse/HIVE-14074
> Project: Hive
> Issue Type: Bug
> Affects Versions: 2.0.1
> Reporter: Abdullah Yousufi
> Assignee: Abdullah Yousufi
> Fix For: 2.2.0
>
> Attachments: HIVE-14074.01.patch
>
>
> Due to HIVE-2573, functions are stored in a per-session registry and only
> loaded in from the metastore when hs2 or hive cli is started. Running RELOAD
> FUNCTION in the current session is a way to force a reload of the functions,
> so that changes that occurred in other running sessions will be reflected in
> the current session, without having to restart the current session. However,
> while functions that are created in other sessions will now appear in the
> current session, functions that have been dropped are not removed from the
> current session's registry. It seems inconsistent that created functions are
> updated while dropped functions are not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
