[
https://issues.apache.org/jira/browse/PIG-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968670#comment-15968670
]
Daniel Dai edited comment on PIG-5223 at 4/14/17 5:54 AM:
----------------------------------------------------------
Yes, you can use the condition (mLimit == -1 && mlimitPlan != null), and if
true, disable the optimization. It is possible to push the limitPlan to
LimitedSortedDataBag, but it is not a one line change and we can do it in
followup.
was (Author: daijy):
Yes, you can use the condition (mLimit == -1 && mlimitPlan != null), and if
true, disable the optimization. It is possible to push the limitPlan to
LimitedSortedDataBag, but it is not a one line change and we can do it in
followup. Please upload the patch.
> TestLimitVariable.testNestedLimitVariable1 and
> TestSecondarySortMR.testNestedLimitedSort failing
> -------------------------------------------------------------------------------------------------
>
> Key: PIG-5223
> URL: https://issues.apache.org/jira/browse/PIG-5223
> Project: Pig
> Issue Type: Bug
> Reporter: Koji Noguchi
> Assignee: Jin Sun
> Fix For: 0.17.0
>
> Attachments: PIG-5223-1.patch
>
>
> TestLimitVariable.testNestedLimitVariable1
> {quote}
> Comparing actual and expected results. expected:<\[(1,11), (2,3), (3,10),
> (6,15)]> but was:<\[(1,11), (2,3), (3,10), (4,11), (5,10), (6,15)]>
> {quote}
> TestSecondarySortMR.testNestedLimitedSort
> {quote}
> Error during parsing. <line 1, column 158> mismatched input 'in' expecting
> INTO
> {quote}
> Latter is probably a simple syntax error. Former looks serious.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
