[
https://issues.apache.org/jira/browse/HIVE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161114#comment-14161114
]
Jason Dere commented on HIVE-2573:
----------------------------------
{quote}
So session-permanent is not possible in the sense that it should be accessible
only for the session.
{quote}
True, permanent functions are not restricted to only being used in one session.
However the function may need to get looked up/loaded for each session that
uses it (see HIVE-6672). As I said earlier though, I think it should ok for
permanent UDFs to go into the system function registry.
{quote}
I think it would be better to investigate META-INF in jar files which should be
added to session, to register temporary functions. How about that?
{quote}
Not sure I understand this - is the idea here to automatically register temp
functions for Jars that the user adds to their session, rather than requiring
users to run CREATE TEMPORARY FUNCTION?
> 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)
