[
https://issues.apache.org/jira/browse/HIVE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156201#comment-14156201
]
Navis commented on HIVE-2573:
-----------------------------
[~jdere] Yes, the concept of this patch is conflicting with permanent functions
which was introduced long after of this. So now we can have four
kind(native/session x permanent/non-permanent) of functions and seemed not a
good idea. To resolve this, I think we should remove session/permanent type and
native/permanent type functions. By doing that, metastore-lookup-twice problem
also would be disappeared.
Currently the HQL grammar is,
{noformat}
create function : native/permanent
create temporary function : native/non-permanent
{noformat}
I'm suggesting like below,
{noformat}
create function : native/permanent
create temporary function : session/non-permanent
{noformat}
For native functions, there would be built-in system functions, which is not
needed to be persisted to metastore.
> 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: Jason Dere
> 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)
