You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/09/03 20:05:52 UTC
[jira] [Commented] (TEZ-402) Define a TezTaskContext for user code
to interact with the AM
[ https://issues.apache.org/jira/browse/TEZ-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756848#comment-13756848 ]
Bikas Saha commented on TEZ-402:
--------------------------------
I would define EventSourceType within the scope of EventSourceInfo and not as an independent enum. It probably has meaning only within the context of an EventSourceInfo.
Events also need a destination index to signify which physical input in the consumer task this event should go to.
Some events may be generated by the AM. These will be System events but System events may also be generated by tasks.
Lot of overlap between the different context objects. Base class?
Dont think vertexId should be exposed in Input/Output. Those are not user facing right? And Input/Output are user facing API's
Why do we need getPhysicalEgdeCount API on the Input/Output. I would expect that in the TezInput/OutputContext.
> Define a TezTaskContext for user code to interact with the AM
> -------------------------------------------------------------
>
> Key: TEZ-402
> URL: https://issues.apache.org/jira/browse/TEZ-402
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Siddharth Seth
> Assignee: Hitesh Shah
> Attachments: TEZ-402.wip.patch
>
>
> A TezTaskContext needs to be provided to I/O/P during initialization. Includes wrapping Umbilical functionality to communicate with the AM, access across I/O/P, etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira