[
https://issues.apache.org/jira/browse/TEZ-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299254#comment-14299254
]
Hadoop QA commented on TEZ-2011:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12695612/TEZ-2011.2.patch
against master revision 21bce95.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 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/107//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/107//console
This message is automatically generated.
> InputReadyVertexManager not resilient to updates in parallelism
> ---------------------------------------------------------------
>
> Key: TEZ-2011
> URL: https://issues.apache.org/jira/browse/TEZ-2011
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-2011.1.patch, TEZ-2011.2.patch
>
>
> It sets up its internal book-keeping upon onVertexStarted() but that
> book-keeping can be wrong if its parallelism changes after that. It needs to
> subscribe to Vertex configured event for its source vertices to make sure
> that all changes have been made before initializing its internal state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
