[
https://issues.apache.org/jira/browse/PIG-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602253#action_12602253
]
Pi Song commented on PIG-159:
-----------------------------
I think it is more appropriate for users to optionally specify input/output
data types as a part of UDF implementation rather than in Pig Script. For
example if I were to implement ArcSin, I would always expect input/output to be
Double. Another missing thing in the proposed syntax is the function
parameter. I think the existing syntax is already good.
> Make changes to the parser to support new types functionality
> -------------------------------------------------------------
>
> Key: PIG-159
> URL: https://issues.apache.org/jira/browse/PIG-159
> Project: Pig
> Issue Type: Sub-task
> Components: impl
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: parser_chages_v10.patch, parser_chages_v11.patch,
> parser_chages_v12.patch, parser_chages_v13.patch, parser_chages_v5.patch,
> parser_chages_v6.patch, parser_chages_v7.patch, parser_chages_v8.patch,
> parser_chages_v9.patch
>
>
> In order to support the new types functionality described in
> http://wiki.apache.org/pig/PigTypesFunctionalSpec, the parse needs to change
> in the following ways:
> 1) AS needs to support types in addition to aliases. So where previously it
> was legal to say:
> a = load 'myfile' as a, b, c;
> it will now also be legal to say
> a = load 'myfile' as a integer, b float, c chararray;
> 2) Non string constants need to be supported. This includes non-string
> atomic types (integer, long, float, double) and the non-atomic types bags,
> tuples, and maps.
> 3) A cast operator needs to be added so that fields can be explicitly casted.
> 4) Changes to DEFINE, to allow users to declare arguments and return types
> for UDFs
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
