[
https://issues.apache.org/jira/browse/HIVE-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-13596:
------------------------------------
Description:
When multiple HS2s are run, creating a permanent fn is only executed on one of
them, and the other HS2s don't get the new function. Unlike say with tables,
where we always get stuff from db on demand, fns are registered at certain
points in the code and if the new one is not registered, it will not be
available.
We could change the code to refresh the udf by name if it's missing, similar to
getting a table or whatever; or we could refresh UDFs when a session is started
in multi-HS2 case, or at some other convenient point.
was:
When multiple HS2s are run, creating a permanent fn is only executed on one of
them, and the other HS2s don't get the new function. Unlike say with tables,
where we always get stuff from db on demand, fns are registered at certain
points in the code and if the new one is not registered, it will not be
available.
We could change the code to refresh the udf by name if it's missing, similar to
getting a table or whatever; or we could refresh UDFs when a session is started
in multi-HS2 case, or in other such logical point.
> HS2 should refresh UDFs for each session, at least in multi-HS2 case
> --------------------------------------------------------------------
>
> Key: HIVE-13596
> URL: https://issues.apache.org/jira/browse/HIVE-13596
> Project: Hive
> Issue Type: Bug
> Reporter: Sergey Shelukhin
>
> When multiple HS2s are run, creating a permanent fn is only executed on one
> of them, and the other HS2s don't get the new function. Unlike say with
> tables, where we always get stuff from db on demand, fns are registered at
> certain points in the code and if the new one is not registered, it will not
> be available.
> We could change the code to refresh the udf by name if it's missing, similar
> to getting a table or whatever; or we could refresh UDFs when a session is
> started in multi-HS2 case, or at some other convenient point.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
