You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2014/10/09 01:32:33 UTC

[jira] [Created] (TEZ-1647) Issue with caching of events in VertexManager::onRootVertexInitialized

Hitesh Shah created TEZ-1647:
--------------------------------

             Summary: Issue with caching of events in VertexManager::onRootVertexInitialized 
                 Key: TEZ-1647
                 URL: https://issues.apache.org/jira/browse/TEZ-1647
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Hitesh Shah
            Assignee: Jeff Zhang


Came across a use-case in Hive where the current functionality does not work. 

Consider a vertex with 2 inputs ( i1, i2 ):

The custom vertex manager in Hive generates events only when both i1 and i2 are initialized. 

Therefore vertexManagerPlugin::onRootInitialized(i1) does nothing but for vertexManagerPLugin::onRootIniitialized(i2) , it calls context.addEvents(i1) and context.addEvents(i2). When this happens, the events generated for i1 never get sent to the VertexImpl to be routed to the tasks. 



  


What this implies is that
  
  





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