hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <>
Subject [jira] [Commented] (HIVE-2573) Create per-session function registry
Date Mon, 25 Apr 2016 21:45:13 GMT


Sergey Shelukhin commented on HIVE-2573:

This patch breaks some scenarios for multi-HS2 deployments, due to the code that talks to
metastore being removed from getFunctionNames(). [~navis] is there a reason why this code
had to be removed? I filed HIVE-13596 before I knew this patch existed (I was assuming the
scenario in HIVE-13596 never worked); restoring the metastore-calling code, possibly with
a config flag, could be one way to fix the issue described there. Ideally, the metastore call
should only happen if the UDF is not found locally; that can be the next step, for now we
can just fix the issue by restoring the old behavior.

> Create per-session function registry 
> -------------------------------------
>                 Key: HIVE-2573
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Server Infrastructure
>            Reporter: Navis
>            Assignee: Navis
>            Priority: Minor
>              Labels: TODOC1.2
>             Fix For: 1.2.0
>         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.14.patch.txt, HIVE-2573.15.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,
> 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

View raw message