hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PIG-1603) dependency created by 'relation as scalar' not captured in graph
Date Thu, 09 Sep 2010 22:09:33 GMT

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

Thejas M Nair updated PIG-1603:

    Attachment: PIG-1603.1.patch

Patch adds a new Logical operator LOScalar . A LogicalOperator that is using  a relation (say
X) as scalar in its inner plan will have a LOScalar added as a predecessor which also have
the relation X as a predecessor. Visitors have been changed to handle this new logical operator.

The test case TestFRJoin2.testConcatenateJobForScalar3  has been enabled.

Results of test-patch -
     [exec] -1 overall.
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     +1 tests included.  The patch appears to include 9 new or modified tests.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec]     -1 release audit.  The applied patch generated 463 release audit warnings
(more than the trunk's current 454 warnings).

Release audit warnings are all related to javadoc file diffs.

> dependency created by 'relation as scalar' not captured in graph
> ----------------------------------------------------------------
>                 Key: PIG-1603
>                 URL: https://issues.apache.org/jira/browse/PIG-1603
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 0.8.0
>         Attachments: PIG-1603.1.patch
> The LogicalOperator that has a ReadScalar udf has a dependency on the relation that is
provides the input to scalar variables. But this is not captured in the graph representation,
and as a result DependencyOrderWalker does not traverse the graph in the real dependency order.
> The testcase TestFRJoin2.testConcatenateJobForScalar3 fails as a result of this issue.
(It has been commented out for now.)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message