[ 
https://issues.apache.org/jira/browse/TEZ-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358204#comment-14358204
 ] 

Hadoop QA commented on TEZ-1094:
--------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12704106/TEZ-1094.3.patch
  against master revision 59529ab.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 5 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-TEZ-Build/285//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/285//console

This message is automatically generated.

> Support pipelined data transfer for Unordered Output
> ----------------------------------------------------
>
>                 Key: TEZ-1094
>                 URL: https://issues.apache.org/jira/browse/TEZ-1094
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Siddharth Seth
>            Assignee: Rajesh Balamohan
>         Attachments: TEZ-1094.1.patch, TEZ-1094.2.patch, TEZ-1094.3.patch
>
>
> For unsorted output (and possibly for sorted output), it should be possible 
> to send data in small batches instead of waiting for everything to be 
> generated before transmitting. For now, planning on getting started with 
> UnsortedOutput / Input pairs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to