hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-1069) [zebra] Order Preserving Sorted Table Union
Date Sat, 07 Nov 2009 17:49:32 GMT

    [ https://issues.apache.org/jira/browse/PIG-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12774644#action_12774644

Hadoop QA commented on PIG-1069:

+1 overall.  Here are the results of testing the latest attachment 
  against trunk revision 833549.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 22 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/142/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/142/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: http://hudson.zones.apache.org/hudson/job/Pig-Patch-h7.grid.sp2.yahoo.net/142/console

This message is automatically generated.

> [zebra] Order Preserving Sorted Table Union
> -------------------------------------------
>                 Key: PIG-1069
>                 URL: https://issues.apache.org/jira/browse/PIG-1069
>             Project: Pig
>          Issue Type: New Feature
>    Affects Versions: 0.6.0
>            Reporter: Yan Zhou
>            Assignee: Yan Zhou
>         Attachments: OrderPreservingSortedTableUnion_svn.patch
> The output schema will adopt a "schema union" semantics, namely, if an output column
only appears in one component table, the result rows will have the values of the column if
the rows are from that component table and null otherwise; on the other hand, if an output
column appears in multiple component tables, the types of the column in all the component
tables must be identical. Otherwise, an exception will be thrown. The result rows will have
the values of the column if the rows are from the component tables that have the column themselves,
or null if otherwise. 
> The order preserving sort-unioned results could be further indexed by the component tables
if the projection contains column(s) named "source_table". If so specified, the component
table index will be output at the position(s) as specified in the projection list. If the
underlying table is not a union of sorted tables, use of the special column name in projection
will cause an exception thrown. 
> If an attempt is made to create a table of a column named "source_table", an excpetion
will be thrown as the name is reserved by zebra for the virtual name. 

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

View raw message