[ https://issues.apache.org/jira/browse/PIG-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969250#comment-15969250 ]
Daniel Dai commented on PIG-5223: --------------------------------- mlimitplan is an expression to calculate limit variable. That is, the number of limited rows is determined at runtime by evaluation expressionPlan (the physical plan equivalence of mlimitplan). If (mLimit == -1 && mlimitPlan != null), that means limiting by variable not constant. It is basically the same as your (mLimit = -1) condition, but add another condition for assurance. > 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)