[
https://issues.apache.org/jira/browse/HIVE-24645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678607#comment-17678607
]
Rajesh Balamohan commented on HIVE-24645:
-----------------------------------------
Just noted that this is causing perf issue in query compilation.Depending on
the query complexity, compiler invokes this multiple times causing high perf
regression in short running queries.
> UDF configure not called when fetch task conversion occurs
> ----------------------------------------------------------
>
> Key: HIVE-24645
> URL: https://issues.apache.org/jira/browse/HIVE-24645
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: John Sherman
> Assignee: John Sherman
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> When hive.fetch.task.conversion kicks in - UDF configure is not called.
> This is likely due to MapredContext not being available when this conversion
> occurs.
> The approach I suggest is to create a dummy MapredContext and provide it with
> the current configuration from ExprNodeGenericFuncEvaluator.
> It is slightly unfortunate that the UDF API relies on MapredContext since
> some aspects of the context do not apply to the variety of engines and
> invocation paths for UDFs which makes it difficult to make a fully formed
> dummy object such as the Reporter objects and the boolean around if it is a
> Map context.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
