You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Siying Dong (JIRA)" <ji...@apache.org> on 2010/09/29 09:15:33 UTC

[jira] Commented: (HIVE-1638) convert commonly used udfs to generic udfs

    [ https://issues.apache.org/jira/browse/HIVE-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916058#action_12916058 ] 

Siying Dong commented on HIVE-1638:
-----------------------------------

Forgot to say, the performance improvement doesn't seem to come from where Joydeep expected. Most improvements seem to come from not converting the second parameter if the return value can be determined only from the first parameter, which we can't do in old UDF functions with UDFBridge wrapper. 

> convert commonly used udfs to generic udfs
> ------------------------------------------
>
>                 Key: HIVE-1638
>                 URL: https://issues.apache.org/jira/browse/HIVE-1638
>             Project: Hadoop Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Namit Jain
>            Assignee: Siying Dong
>         Attachments: HIVE-1638.1.patch
>
>
> Copying a mail from Joy:
> i did a little bit of profiling of a simple hive group by query today. i was surprised to see that one of the most expensive functions were in converting the equals udf (i had some simple string filters) to generic udfs. (primitiveobjectinspectorconverter.textconverter)
> am i correct in thinking that the fix is to simply port some of the most popular udfs (string equality/comparison etc.) to generic udsf?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.