[
https://issues.apache.org/jira/browse/HIVE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868485#comment-13868485
]
Edward Capriolo commented on HIVE-6167:
---------------------------------------
In my opinion we must keep the current syntax working as is. Current users of
hive do not want there scripts to break just to match a standard. If we wish to
add new syntax that matches a given standard that makes sense. I do not think
the current standard forbids keeping our current syntax and functionality. Also
realistically we have to be practical. Users have sessions, most users are not
going to care what database/schema a function is associated with. Most are
going to want global functions. Most people are not going to have so many
functions that a conflict would ever arise. Lets not make and solve problems we
really don't have.
> Allow user-defined functions to be qualified with database name
> ---------------------------------------------------------------
>
> Key: HIVE-6167
> URL: https://issues.apache.org/jira/browse/HIVE-6167
> 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
(v6.1.5#6160)
