[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285010#comment-17285010
]
Hadoop QA 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 6s{color}
| {color:red} TEZ-3866 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 ||
| JIRA Issue | TEZ-3866 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12931385/TEZ-3866.2.patch |
| Console output |
https://ci-hadoop.apache.org/job/PreCommit-TEZ-Build/100/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)
[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17285008#comment-17285008
]
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)
[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542285#comment-16542285
]
TezQA commented on TEZ-3866:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12931385/TEZ-3866.2.patch
against master revision 4496f66.
{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 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.dag.app.TestSpeculation
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2861//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2861//console
This message is 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
(v7.6.3#76005)
[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[
https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542186#comment-16542186
]
TezQA commented on TEZ-3866:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12931370/TEZ-3866.1.patch
against master revision 4496f66.
{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:red}-1 findbugs{color}. The patch appears to introduce 5 new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.test.TestAMRecovery
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2859//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TEZ-Build/2859//artifact/patchprocess/newPatchFindbugsWarningstez-api.html
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2859//console
This message is 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
>
>
> 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
(v7.6.3#76005)
[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[ https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16542177#comment-16542177 ] ASF GitHub Bot commented on TEZ-3866: - GitHub user beltran opened a pull request: https://github.com/apache/tez/pull/27 TEZ-3866: add ability to pass information between plugins You can merge this pull request into a Git repository by running: $ git pull https://github.com/beltran/tez TEZ-3866 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tez/pull/27.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #27 commit b399012385994f239243f769b3ed4389b1ab1035 Author: Jaume Marhuenda Date: 2018-07-11T02:14:51Z TEZ-3866: add ability to pass information between plugins > 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 > > > 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 (v7.6.3#76005)
[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[ https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255902#comment-16255902 ] Eric Wohlstadter commented on TEZ-3866: --- [~sershe] I'll take a look at it today. Let's synch up on phone tomorrow. [~aplusplus] is out next week. > 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 > > 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 (v6.4.14#64029)
[jira] [Commented] (TEZ-3866) add ability to pass information between plugins
[ https://issues.apache.org/jira/browse/TEZ-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16254677#comment-16254677 ] Sergey Shelukhin commented on TEZ-3866: --- cc [~hagleitn] [~aplusplus] this is needed for Hive workload management to avoid some major ugly code that exists right now :) > 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 > > Distinct from TEZ-3815, since even with the 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. There doesn't seem to be any > means to do it now. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
