[
https://issues.apache.org/jira/browse/HIVE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157034#comment-14157034
]
Jason Dere commented on HIVE-2573:
----------------------------------
Agreed that it makes sense to get rid of the native/non-permanent functions.
I could see a case for the permanent (metastore) UDFs being added to the
session function registry, just because it would keep the system registry clean
with just built-in functions. Also even if the permanent UDF is in the system
registry, Session's classloader may not have loaded the Jars necessary for the
UDF, if it was a different thread which added the UDF to the system registry.
Although I guess HIVE-6672 should take care of that issue. Anyway it looks like
the permanent UDFs will work ok either as native/permanent or session/permanent
so either way should do.
> Create per-session function registry
> -------------------------------------
>
> Key: HIVE-2573
> URL: https://issues.apache.org/jira/browse/HIVE-2573
> Project: Hive
> Issue Type: Improvement
> Components: Server Infrastructure
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2573.D3231.1.patch,
> HIVE-2573.1.patch.txt, HIVE-2573.2.patch.txt, HIVE-2573.3.patch.txt,
> HIVE-2573.4.patch.txt
>
>
> Currently the function registry is shared resource and could be overrided by
> other users when using HiveServer. If per-session function registry is
> provided, this situation could be prevented.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
