hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuefu Zhang (JIRA)" <>
Subject [jira] [Commented] (HIVE-6167) Allow user-defined functions to be qualified with database name
Date Fri, 10 Jan 2014 22:04:50 GMT


Xuefu Zhang commented on HIVE-6167:

I largely agree except for one thought on #2. If a user adds a perm function without db name,
could we assume it's global. Image an admin register a particular function across all DBs.
If Hive insists the function go to a DB, then he/she will have to do the same for each DB:
use DB1;
create function a();
use Db2;
create function a();

create function DB1.a();
create function DB1.a();

It becomes much simpler if a function without DB name goes global (in line with temp functions).
Is this completely anti SQL standard? Even so, It seems that usability outweighs, not to mention
that Hive function is non-standard anyway.

> Allow user-defined functions to be qualified with database name
> ---------------------------------------------------------------
>                 Key: HIVE-6167
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: UDF
>            Reporter: Jason Dere
>            Assignee: Jason Dere
> Function names in Hive are currently unqualified and there is a single namespace for
all function names. This task would allow users to define temporary UDFs (and eventually permanent
UDFs) with a database name, such as:
> CREATE TEMPORARY FUNCTION userdb.myfunc 'myudfclass';

This message was sent by Atlassian JIRA

View raw message