You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2009/05/05 21:13:30 UTC
[jira] Commented: (HIVE-45) Hive: GenericUDF and support of complex
object
[ https://issues.apache.org/jira/browse/HIVE-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706163#action_12706163 ]
Edward Capriolo commented on HIVE-45:
-------------------------------------
I just put in a Jira for [https://issues.apache.org/jira/browse/HIVE-471]. I realize this jira adds support for some if not all of the things I was looking to do.
Without getting over generic I would have liked to support.
{noformat}
evalautate(String, String,Object[])
{noformat}
As well as
{noformat}
evaluate( evalautate(String, String,Object[]), "getName", "this", "that")
{noformat}
It seems like what you are doing here makes that possible.
> Hive: GenericUDF and support of complex object
> ----------------------------------------------
>
> Key: HIVE-45
> URL: https://issues.apache.org/jira/browse/HIVE-45
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Zheng Shao
> Assignee: Zheng Shao
> Fix For: 0.4.0
>
>
> GenericUDF are more powerful than UDF in the following ways:
> 1. It can accept arguments of complex types, and return complex types.
> 2. It can accept variable length of arguments.
> 3. It can accept an infinite number of function signature - for example, it's easy to write a GenericUDF that accepts array<int>, array<array<int>> and so on (arbitrary levels of nesting).
> 4. It can do short-circuit evaluations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.