hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abdullah Yousufi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-14074) RELOAD FUNCTION should update dropped functions
Date Wed, 22 Jun 2016 19:09:19 GMT

    [ https://issues.apache.org/jira/browse/HIVE-14074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344987#comment-15344987
] 

Abdullah Yousufi commented on HIVE-14074:
-----------------------------------------

Ah that's a good point. I had considered the set removal method, but was curious if this one-liner
would work. I'll implement it that way instead.

> 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)

Mime
View raw message