You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pig.apache.org by "Rohini Palaniswamy (JIRA)" <ji...@apache.org> on 2016/01/08 22:17:39 UTC

[jira] [Updated] (PIG-4773) [Pig on Tez] Secondary key descending sort in nested foreach after union does ascending instead

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

Rohini Palaniswamy updated PIG-4773:
------------------------------------
    Attachment: PIG-4773-1.patch

> [Pig on Tez] Secondary key descending sort in nested foreach after union does ascending instead
> -----------------------------------------------------------------------------------------------
>
>                 Key: PIG-4773
>                 URL: https://issues.apache.org/jira/browse/PIG-4773
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Rohini Palaniswamy
>            Assignee: Rohini Palaniswamy
>             Fix For: 0.16.0
>
>         Attachments: PIG-4773-1.patch
>
>
>   PigSecondaryKeyComparator does not implement a compare(WritableComparable a, WritableComparable b) method. In case of  OrderedGroupedMergedKVInput with vertex groups, object comparison instead of byte comparison is done when merging the multiple inputs into one. Since the compare API is not overridden, WritableComparator compare API is called and  the value types are directly compared which means it is always ascending.



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