[
https://issues.apache.org/jira/browse/PIG-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614550#action_12614550
]
Alan Gates commented on PIG-320:
--------------------------------
Pi, since much of these changes are in the type checker, I'd like to get your
feedback on them.
One comment from me. Why do POForeach and POCogroup have resetSchema() in
addition to unsetSchema()? Shouldn't their unsetSchema methods do the work
that's in resetSchema? Is there ever a case you'll want to unset the foreach's
schema with unsetting it's plan's schemas?
> 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.
