You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Santhosh Srinivasan (JIRA)" <ji...@apache.org> on 2008/12/03 20:37:44 UTC
[jira] Updated: (PIG-320) The parser/type checker should use the
getSchema method of UDFs to deduce return type/schema
[ https://issues.apache.org/jira/browse/PIG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Santhosh Srinivasan updated PIG-320:
------------------------------------
Patch Info: [Patch Available]
> The parser/type checker should use the getSchema method of UDFs to deduce return type/schema
> --------------------------------------------------------------------------------------------
>
> Key: PIG-320
> URL: https://issues.apache.org/jira/browse/PIG-320
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: types_branch
> Reporter: Santhosh Srinivasan
> Assignee: Santhosh Srinivasan
> Fix For: types_branch
>
> Attachments: udf_outputSchema.patch
>
>
> Currently, the parser/type checker uses the getReturnType to deduce the return type of the user defined function (UDF). This mechanism is satisfactory only for basic types (int, long, ...); for composite types (tuple, bag), the schema is also required.The abstract class EvalFunc interface exposes the outputSchema to deduce the return type/schema of the UDF. The parser/type checker should use this method to figure out the return type/schema of the UDF and use it appropriately.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.