[
https://issues.apache.org/jira/browse/HIVE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234923#comment-14234923
]
Jason Dere commented on HIVE-2573:
----------------------------------
Is this one still being worked on? I think it's basically ready, with the
exception of 2 questions/comments from the RB of patch v13:
- HiveParser.g has a error message that should be changed from "drop function
statement" to "reload function statement"
- SessionConf.java: What about the idea of moving static call to
resolveFunctions() to SessionState? I thought that would remove the need for
SessionConf, because then Hive class would once again be usable during query
runtime. Unless you think it's cleaner to use SessionConf to get HiveConf
rather than the Hive object.
> 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: Navis
> Priority: Minor
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2573.D3231.1.patch,
> HIVE-2573.1.patch.txt, HIVE-2573.10.patch.txt, HIVE-2573.11.patch.txt,
> HIVE-2573.12.patch.txt, HIVE-2573.13.patch.txt, HIVE-2573.2.patch.txt,
> HIVE-2573.3.patch.txt, HIVE-2573.4.patch.txt, HIVE-2573.5.patch,
> HIVE-2573.6.patch, HIVE-2573.7.patch, HIVE-2573.8.patch.txt,
> HIVE-2573.9.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)
