[ 
https://issues.apache.org/jira/browse/PIG-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763236#action_12763236
 ] 

Thejas M Nair commented on PIG-999:
-----------------------------------


In previous comment
{code}
o = order f by $2;
{code}
should have been -
{code}
o = order f by $1;
{code}


> sorting on map-value fails if map-value is not of bytearray type
> ----------------------------------------------------------------
>
>                 Key: PIG-999
>                 URL: https://issues.apache.org/jira/browse/PIG-999
>             Project: Pig
>          Issue Type: Sub-task
>            Reporter: Thejas M Nair
>
> When query execution plan is created by pig, it assumes the type to be 
> bytearray because there is no schema information associated with map fields.
> But at run time, the loader might return the actual type. This results in a 
> ClassCastException.
> This issue points to the larger issue of the way pig is handling types for 
> map-value. 
> This issue should be fixed in the context of revisiting the frontend logic 
> and pig-latin semantics.
> This is related to PIG-880 . The patch in PIG-880 changed PigStorage to 
> always return bytearray for map values to work around this, but other loaders 
> like BinStorage can return the actual type causing this issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to