[
https://issues.apache.org/jira/browse/PIG-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gianmarco De Francisci Morales updated PIG-1926:
------------------------------------------------
Attachment: PIG-1926.patch
First working version for LIMIT.
POLimit correctly evaluates the limit at runtime.
AllExpressionVisitor visits LOLimit, discovers the scalar expression and
correctly sets the plan.
Visitors do the visit only if the plan has been set, so the normal code path is
not disrupted.
Is there a consistent formatting template for Pig in order to make the patch
more readable? (half of the modified lines are from the code formatter).
Next steps:
Evaluate the interaction with optimizers.
Translate the script used for testing into a unit test for the feature.
> Sample/Limit should take scalar
> -------------------------------
>
> Key: PIG-1926
> URL: https://issues.apache.org/jira/browse/PIG-1926
> Project: Pig
> Issue Type: Improvement
> Reporter: Daniel Dai
> Labels: gsoc2011
> Attachments: PIG-1926.patch, PIG-1926.patch
>
>
> Currently, Limit, Sample only takes a constant. It would be better we can use
> a scalar in the place of constant. Eg:
> {code}
> a = load 'a.txt';
> b = group a all;
> c = foreach b generate COUNT(a) as sum;
> d = order a by $0;
> e = limit d c.sum/100;
> {code}
> This is a candidate project for Google summer of code 2011. More information
> about the program can be found at http://wiki.apache.org/pig/GSoc2011
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
