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

Tez CI commented on TEZ-3866:
-----------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  5s{color} 
| {color:red} https://github.com/apache/tez/pull/27 does not apply to master. 
Rebase required? Wrong Branch? See 
https://cwiki.apache.org/confluence/display/TEZ/How+to+Contribute+to+Tez for 
help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| GITHUB PR | https://github.com/apache/tez/pull/27 |
| JIRA Issue | TEZ-3866 |
| Console output | 
https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-27/1/console |
| versions | git=2.17.1 |
| Powered by | Apache Yetus 0.12.0 https://yetus.apache.org |


This message was automatically generated.



> add ability to pass information between plugins
> -----------------------------------------------
>
>                 Key: TEZ-3866
>                 URL: https://issues.apache.org/jira/browse/TEZ-3866
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Jaume M
>            Priority: Major
>         Attachments: TEZ-3866.1.patch, TEZ-3866.2.patch
>
>
> Distinct from TEZ-3815, since even with a hack that makes plugins aware of 
> each other, they cannot store task-specific info without calling into each 
> others' per-task structures.
> In particular, I need a piece of info that is generated when the custom 
> scheduler calls getContext().taskAllocated, to be propagated to communicator 
> plugin registerRunningTaskAttempt, so that the custom communicator could 
> include additional info in task submission (e.g. a scheduler-specific 
> priority or other instructions). There doesn't seem to be any means to do it 
> now.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to