[
https://issues.apache.org/jira/browse/HIVE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854695#comment-13854695
]
Jason Dere commented on HIVE-6047:
----------------------------------
Thanks for the feedback.
1. Yeah, will provide some design details. Still need to think though some of
this.
2. Definitely will be metastore changes - will provide those as part of the
design details.
3. I wasn't aware of any CREATE FUNCTION spec in the SQL standard .. is there
one?
4. True, the db name ends up being more of a namespace, but I was under the
impression that Hive databases were more like a schema name. Even if a user
has specified "use database A", are they still able to select/join data from a
table in another database? I thought this was the case.
5. Do you mean it should read "Sets of JARs/files/archives can be saved .."?
Sure, will fix.
6. If we are able to create them using a database name, then yes it would make
sense to be able to specify the DB name to get the jar/file/archive sets for
that database. Without a db name, then I guess it would default to the current
database.
> Permanent UDFs in Hive
> ----------------------
>
> Key: HIVE-6047
> URL: https://issues.apache.org/jira/browse/HIVE-6047
> Project: Hive
> Issue Type: Bug
> Components: UDF
> Reporter: Jason Dere
> Assignee: Jason Dere
> Attachments: PermanentFunctionsinHive.pdf
>
>
> Currently Hive only supports temporary UDFs which must be re-registered when
> starting up a Hive session. Provide some support to register permanent UDFs
> with Hive.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
