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 2015/09/28 22:50:04 UTC

[jira] [Comment Edited] (TEZ-2851) Support a way for upstream applications to pass in a caller context to Tez

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

Hitesh Shah edited comment on TEZ-2851 at 9/28/15 8:49 PM:
-----------------------------------------------------------

bq. A key-value pair for the context may be useful instead of specific fields.

I consider this but left it as a potential future enhancement where the caller can add any form of key-value tags to the DAG or a Tez session. This could be any identifiers or could potentially also be used to store any chain of information to track the full lineage. For now, I basically went with a very defined API to track the immediate caller ( i.e. parent ). If you were implying a need for a general key-val tag/map, is that something you would like to see in this jira or is it ok to add in a future jira? 

bq. Are any of the fields in CallerContext Nullable ?

Only description can be null at any point in time. CallerId+Type are potentially optional but can never be null if either is specified. Will add @Nullable to desc. 




was (Author: hitesh):
bq. A key-value pair for the context may be useful instead of specific fields.

I consider this but left it as a potential future enhancement where the caller can add any form of key-value tags to the DAG or a Tez session. This could be any identifiers or could potentially also be used to store any chain of information to track the full lineage. For now, I basically went with a very defined API to track the immediate caller ( i.e. parent ). If you were implying a need for a general key-val tag/map, is that something you would like to see in this jira or is it ok to add in a future jira? 

bq. Are any of the fields in CallerContext Nullable ?

Only description can be null at any point in time. CallerId+Type are potentially optional but can never be null if either is specified. 



> Support a way for upstream applications to pass in a caller context to Tez
> --------------------------------------------------------------------------
>
>                 Key: TEZ-2851
>                 URL: https://issues.apache.org/jira/browse/TEZ-2851
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>         Attachments: TEZ-2851.1.patch, TEZ-2851.2.patch, TEZ-2851.3.patch, TEZ-2851.4.patch
>
>




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