[jira] [Updated] (PIG-1967) deprecate current syntax for casting relation as scalar, to use explicit cast to tuple

["Daniel Dai (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PIG-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Dai updated PIG-1967:
----------------------------
    Fix Version/s:     (was: 0.15.0)
                   0.16.0

> deprecate current syntax for casting relation as scalar, to use explicit cast to tuple
> --------------------------------------------------------------------------------------
>
>                 Key: PIG-1967
>                 URL: https://issues.apache.org/jira/browse/PIG-1967
>             Project: Pig
>          Issue Type: Improvement
>    Affects Versions: 0.8.0, 0.9.0
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 0.16.0
>
>         Attachments: PIG-1967.0.patch
>
>
> When the feature added in PIG-1434, there was a proposal to cast it to tuple, to be able to use as a scalar. But for some reason, in the implementation this cast was not required.
> See -
> https://issues.apache.org/jira/browse/PIG-1434?focusedCommentId=12888449&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12888449
> The current syntax which does not need this cast seems to lead to lot of confusion among users, who end up using this feature unintentionally. This usually happens because the user is referring to the bag column(s) in output of (co)group using a wrong name, which happens to be another relation. Often, users realize the mistake only at runtime. New users, will have trouble figuring out what was wrong.
> I think we should support the use of the cast as originally proposed, and deprecate the current syntax. The warning issued when the deprecated syntax is used is likely to help users realize that they have unintentionally used this feature.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)