You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Olga Natkovich (JIRA)" <ji...@apache.org> on 2010/01/05 20:19:54 UTC
[jira] Updated: (PIG-1171) Top-N queries produce incorrect results
when followed by a cross statement
[ https://issues.apache.org/jira/browse/PIG-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olga Natkovich updated PIG-1171:
--------------------------------
Affects Version/s: 0.6.0
Fix Version/s: 0.7.0
> Top-N queries produce incorrect results when followed by a cross statement
> --------------------------------------------------------------------------
>
> Key: PIG-1171
> URL: https://issues.apache.org/jira/browse/PIG-1171
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.7.0
>
> Attachments: PIG-1171.patch
>
>
> ??I am not sure if this is a bug, or something more subtle, but here is the problem that I am having.??
> ??When I LOAD a dataset, change it with an ORDER, LIMIT it, then CROSS it with itself, the results are not correct. I expect to see the cross of the limited, ordered dataset, but instead I see the cross of the limited dataset. Effectively, its like the LIMIT is being excluded.??
> ??Example code follows:??
> {code}
> A = load 'foo' as (f1:int, f2:int, f3:int); B = load 'foo' as (f1:int, f2:int, f3:int);
> a = ORDER A BY f1 DESC;
> b = ORDER B BY f1 DESC;
> aa = LIMIT a 1;
> bb = LIMIT b 1;
> C = CROSS aa, bb;
> DUMP C;
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.