You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Dmitriy V. Ryaboy (Assigned) (JIRA)" <ji...@apache.org> on 2011/12/14 19:25:30 UTC

[jira] [Assigned] (PIG-2427) getSchemaFromString throws away the name of the tuple that is in a bag

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

Dmitriy V. Ryaboy reassigned PIG-2427:
--------------------------------------

    Assignee: Jonathan Coveney
    
> getSchemaFromString throws away the name of the tuple that is in a bag
> ----------------------------------------------------------------------
>
>                 Key: PIG-2427
>                 URL: https://issues.apache.org/jira/browse/PIG-2427
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.11
>            Reporter: Jonathan Coveney
>            Assignee: Jonathan Coveney
>            Priority: Minor
>             Fix For: 0.11
>
>         Attachments: PIG2427.patch
>
>
> {code}Schema thing = Utils.getSchemaFromString("b:bag{t:tuple(x:int,y:int,z:int)}");
> System.out.println(thing.getField(0).schema.getField(0).alias); //returns null{code}
> This isn't a huge issue, but it does seem odd to throw away this information unnecessarily. While any bag will of course have thus tuple and no other elements, it seems to violate the principle of least astonishment: if the tuple name was specified, shouldn't it be kept around?
> Edit: I just found a case where this actually can be a bit annoying. If you want to pull that tuple out of the bag, for whatever reason, you've now lost its name.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira