[
https://issues.apache.org/jira/browse/HIVE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150214#comment-13150214
]
Carl Steinbach commented on HIVE-2573:
--------------------------------------
bq. I've thought keyword 'TEMPORARY' could mean the 'session' thing but it
seemed to be not safe.
What issues did you run into? I think the original intent of the 'TEMPORARY'
keyword was to signal that the function's lifecycle is tied to the session.
Adding a new SESSION keyword seems to imply that non-SESSION TEMPORARY
functions should be globally visible, which doesn't seem like a good idea.
If we currently have tests that rely on TEMPORARY functions being visible to
other sessions, then maybe we should instead support 'CREATE [TEMPORARY]
FUNCTION ...', mapping 'CREATE FUNCTION ...' to the current behavior, and
'CREATE TEMPORARY FUNCTION ...' to the new behavior added in this patch.
> 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
> Priority: Minor
> Attachments: HIVE-2573.1.patch.txt, HIVE-2573.2.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
