[jira] [Commented] (TEZ-3269) Provide basic fair routing and scheduling functionality via custom VertexManager and EdgeManager
[
https://issues.apache.org/jira/browse/TEZ-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15544146#comment-15544146
]
TezQA commented on TEZ-3269:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831443/TEZ-3269-3.patch
against master revision ad1fb62.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2008//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2008//console
This message is automatically generated.
> Provide basic fair routing and scheduling functionality via custom
> VertexManager and EdgeManager
>
>
> Key: TEZ-3269
> URL: https://issues.apache.org/jira/browse/TEZ-3269
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Ming Ma
> Attachments: TEZ-3269-2.patch, TEZ-3269-3.patch, TEZ-3269.patch
>
>
> With TEZ-3206 and TEZ-3216, we can build a custom VertexManager and
> EdgeManager that uses partition stats to do fair routing as well as the
> scheduling based on destination tasks’ dependency on source tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Success: TEZ-3269 PreCommit Build #2008
Jira: https://issues.apache.org/jira/browse/TEZ-3269
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2008/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4823 lines...]
[INFO] Tez SUCCESS [ 0.028 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:01 h
[INFO] Finished at: 2016-10-04T02:44:32+00:00
[INFO] Final Memory: 80M/1350M
[INFO]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831443/TEZ-3269-3.patch
against master revision ad1fb62.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2008//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2008//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
0fb0ea9b2d84cf61f5f50946a24a209858273f8a logged out
==
==
Finished build.
==
==
Archiving artifacts
[description-setter] Description set: TEZ-3269
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Updated] (TEZ-3269) Provide basic fair routing and scheduling functionality via custom VertexManager and EdgeManager
[ https://issues.apache.org/jira/browse/TEZ-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ming Ma updated TEZ-3269: - Attachment: TEZ-3269-3.patch Thank you [~aplusplus]! The new patch has addressed the issues you raised. Regarding "why pendingTasks.size() would be zero?", it might be due to some test case with the the number of destination tasks set to zero and the old FairShufleVertexManager handling. > Provide basic fair routing and scheduling functionality via custom > VertexManager and EdgeManager > > > Key: TEZ-3269 > URL: https://issues.apache.org/jira/browse/TEZ-3269 > Project: Apache Tez > Issue Type: Sub-task >Reporter: Ming Ma > Attachments: TEZ-3269-2.patch, TEZ-3269-3.patch, TEZ-3269.patch > > > With TEZ-3206 and TEZ-3216, we can build a custom VertexManager and > EdgeManager that uses partition stats to do fair routing as well as the > scheduling based on destination tasks’ dependency on source tasks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3443) Remove a repeated method
[ https://issues.apache.org/jira/browse/TEZ-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543918#comment-15543918 ] Zhiyuan Yang commented on TEZ-3443: --- This method is there for compatibility to original mapreduce. I'm afraid removing this can potentially cause some legacy user code to fail. > Remove a repeated method > > > Key: TEZ-3443 > URL: https://issues.apache.org/jira/browse/TEZ-3443 > Project: Apache Tez > Issue Type: Improvement >Affects Versions: 0.8.4 >Reporter: darion yaphet >Assignee: darion yaphet >Priority: Minor > Attachments: TEZ-3443.1.patch > > > MRTask.getFsStatistics seems not used , I try to remove it . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2658) Create a CLI utility tool to track Tez DAG/Application Stats
[ https://issues.apache.org/jira/browse/TEZ-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543220#comment-15543220 ] Piyush Narang commented on TEZ-2658: hey [~jeagles] / [~hitesh]. The jira that I was working on to add some APIs is here: https://issues.apache.org/jira/browse/TEZ-3369 (associated PR: https://github.com/apache/tez/pull/13). Unfortunately I haven't had the time to work on some of Hitesh's feedback. Got pulled into a few other tasks at work. I think I should be able to pick it back up in the next 2-3 weeks. I don't want to block you if you need it more urgently. So if you'd like to pick it up, let me know. > Create a CLI utility tool to track Tez DAG/Application Stats > > > Key: TEZ-2658 > URL: https://issues.apache.org/jira/browse/TEZ-2658 > Project: Apache Tez > Issue Type: Improvement >Reporter: Saikat >Assignee: Saikat > Attachments: TEZ-2658.1.patch, TEZ-2658.2.patch, TEZ-2658.3.patch, > TEZ-2658.4.patch, TEZ-2658.5.patch, TEZ-2658.6.patch, TEZ-2658.7.patch, > TEZ-2658.8.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2658) Create a CLI utility tool to track Tez DAG/Application Stats
[ https://issues.apache.org/jira/browse/TEZ-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543129#comment-15543129 ] Jonathan Eagles commented on TEZ-2658: -- It looks likes the current patch here on TEZ-2658 supersedes TEZ-1622 and has quite a lot of functionality. If [~pnarang] is willing to take over this effort, is there a jira (this one?), that can be used to track this effort? > Create a CLI utility tool to track Tez DAG/Application Stats > > > Key: TEZ-2658 > URL: https://issues.apache.org/jira/browse/TEZ-2658 > Project: Apache Tez > Issue Type: Improvement >Reporter: Saikat >Assignee: Saikat > Attachments: TEZ-2658.1.patch, TEZ-2658.2.patch, TEZ-2658.3.patch, > TEZ-2658.4.patch, TEZ-2658.5.patch, TEZ-2658.6.patch, TEZ-2658.7.patch, > TEZ-2658.8.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-2658) Create a CLI utility tool to track Tez DAG/Application Stats
[ https://issues.apache.org/jira/browse/TEZ-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15543001#comment-15543001 ] Hitesh Shah commented on TEZ-2658: -- [~jeagles] I think [~pnarang] was looking at making some changes to the client which would help some of this work. > Create a CLI utility tool to track Tez DAG/Application Stats > > > Key: TEZ-2658 > URL: https://issues.apache.org/jira/browse/TEZ-2658 > Project: Apache Tez > Issue Type: Improvement >Reporter: Saikat >Assignee: Saikat > Attachments: TEZ-2658.1.patch, TEZ-2658.2.patch, TEZ-2658.3.patch, > TEZ-2658.4.patch, TEZ-2658.5.patch, TEZ-2658.6.patch, TEZ-2658.7.patch, > TEZ-2658.8.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3269) Provide basic fair routing and scheduling functionality via custom VertexManager and EdgeManager
[
https://issues.apache.org/jira/browse/TEZ-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542944#comment-15542944
]
Zhiyuan Yang commented on TEZ-3269:
---
I'm sorry for the late review...
Generally code looks good as core parts are mostly same wtih TEZ-3209 patch.
Just some minor things:
In FairShuffleVertexManager:
{code:java}
if (pendingTasks.size() == 0) {
// don't change routing when number of tasks is set to zero.
return null;
}
{code}
Given initial parallelism of reducer determines the number of partitions of
source vertices output, why pendingTasks.size() would be zero?
In Test FairShuffleVertexManager:
{code:java}
// The 2nd destination task fetches one partition from the first source
// task.
// The 3rd destination task fetches one partition from the 2nd and 3rd
// source task.
{code}
The comments doesn't match code.
{code:java}
Assert.assertTrue(manager.config.isAutoParallelismEnabled() == true);
{code}
'== true' can be removed.
> Provide basic fair routing and scheduling functionality via custom
> VertexManager and EdgeManager
>
>
> Key: TEZ-3269
> URL: https://issues.apache.org/jira/browse/TEZ-3269
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Ming Ma
> Attachments: TEZ-3269-2.patch, TEZ-3269.patch
>
>
> With TEZ-3206 and TEZ-3216, we can build a custom VertexManager and
> EdgeManager that uses partition stats to do fair routing as well as the
> scheduling based on destination tasks’ dependency on source tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (TEZ-3269) Provide basic fair routing and scheduling functionality via custom VertexManager and EdgeManager
[
https://issues.apache.org/jira/browse/TEZ-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542944#comment-15542944
]
Zhiyuan Yang edited comment on TEZ-3269 at 10/3/16 5:39 PM:
I'm sorry for the late review...
Generally code looks good as core parts are mostly same wtih TEZ-3209 patch.
Just some minor things:
In FairShuffleVertexManager:
{code:java}
if (pendingTasks.size() == 0) {
// don't change routing when number of tasks is set to zero.
return null;
}
{code}
Given initial parallelism of reducer determines the number of partitions of
source vertices output, why pendingTasks.size() would be zero?
In TestFairShuffleVertexManager:
{code:java}
// The 2nd destination task fetches one partition from the first source
// task.
// The 3rd destination task fetches one partition from the 2nd and 3rd
// source task.
{code}
The comments doesn't match code.
{code:java}
Assert.assertTrue(manager.config.isAutoParallelismEnabled() == true);
{code}
'== true' can be removed.
was (Author: aplusplus):
I'm sorry for the late review...
Generally code looks good as core parts are mostly same wtih TEZ-3209 patch.
Just some minor things:
In FairShuffleVertexManager:
{code:java}
if (pendingTasks.size() == 0) {
// don't change routing when number of tasks is set to zero.
return null;
}
{code}
Given initial parallelism of reducer determines the number of partitions of
source vertices output, why pendingTasks.size() would be zero?
In Test FairShuffleVertexManager:
{code:java}
// The 2nd destination task fetches one partition from the first source
// task.
// The 3rd destination task fetches one partition from the 2nd and 3rd
// source task.
{code}
The comments doesn't match code.
{code:java}
Assert.assertTrue(manager.config.isAutoParallelismEnabled() == true);
{code}
'== true' can be removed.
> Provide basic fair routing and scheduling functionality via custom
> VertexManager and EdgeManager
>
>
> Key: TEZ-3269
> URL: https://issues.apache.org/jira/browse/TEZ-3269
> Project: Apache Tez
> Issue Type: Sub-task
>Reporter: Ming Ma
> Attachments: TEZ-3269-2.patch, TEZ-3269.patch
>
>
> With TEZ-3206 and TEZ-3216, we can build a custom VertexManager and
> EdgeManager that uses partition stats to do fair routing as well as the
> scheduling based on destination tasks’ dependency on source tasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (TEZ-2658) Create a CLI utility tool to track Tez DAG/Application Stats
[ https://issues.apache.org/jira/browse/TEZ-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542867#comment-15542867 ] Jonathan Eagles commented on TEZ-2658: -- [~saikatr], pinging you to see if you are still working on this patch. Otherwise, I'll try to find someone in the community to take up this effort. > Create a CLI utility tool to track Tez DAG/Application Stats > > > Key: TEZ-2658 > URL: https://issues.apache.org/jira/browse/TEZ-2658 > Project: Apache Tez > Issue Type: Improvement >Reporter: Saikat >Assignee: Saikat > Attachments: TEZ-2658.1.patch, TEZ-2658.2.patch, TEZ-2658.3.patch, > TEZ-2658.4.patch, TEZ-2658.5.patch, TEZ-2658.6.patch, TEZ-2658.7.patch, > TEZ-2658.8.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3433: Target Version/s: 0.9.0, 0.8.5 (was: 0.9.0, 0.8.4) > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.v2.patch > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sreenath Somarajapuram updated TEZ-3433: Target Version/s: 0.8.4, 0.9.0 (was: 0.9.0) > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.v2.patch > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[
https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541839#comment-15541839
]
TezQA commented on TEZ-3433:
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831275/TEZ-3433.v2.patch
against master revision 5c2f893.
{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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2007//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2007//console
This message is automatically generated.
> Tez UI: Searching using wrong ID causes error in all DAGs page
> --
>
> Key: TEZ-3433
> URL: https://issues.apache.org/jira/browse/TEZ-3433
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Sreenath Somarajapuram
>Assignee: Sushmitha Sreenivasan
> Attachments: TEZ-3433.patch, TEZ-3433.v2.patch
>
>
> - In All DAGs page, DAG id uses an implementation separate from other search
> parameters.
> - It throws error on trying to search with a wrong ID.
> - Fix the UI to display a "No records available!" message, similar to the one
> we display on giving a wrong value in other fields.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Success: TEZ-3433 PreCommit Build #2007
Jira: https://issues.apache.org/jira/browse/TEZ-3433
Build: https://builds.apache.org/job/PreCommit-TEZ-Build/2007/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 4812 lines...]
[INFO] Tez SUCCESS [ 0.022 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 56:25 min
[INFO] Finished at: 2016-10-03T08:06:02+00:00
[INFO] Final Memory: 81M/1491M
[INFO]
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831275/TEZ-3433.v2.patch
against master revision 5c2f893.
{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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2007//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2007//console
This message is automatically generated.
==
==
Adding comment to Jira.
==
==
Comment added.
02fdcd02ce493f2c3cce46377b238601e5a65f09 logged out
==
==
Finished build.
==
==
Archiving artifacts
[description-setter] Description set: TEZ-3433
Recording test results
Email was triggered for: Success
Sending email for trigger: Success
###
## FAILED TESTS (if any)
##
All tests passed
[jira] [Commented] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15541706#comment-15541706 ] Sreenath Somarajapuram commented on TEZ-3433: - +1 LGTM. Waiting for pre-commit build. > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.v2.patch > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushmitha Sreenivasan updated TEZ-3433: --- Attachment: (was: TEZ-3433.v2.patch) > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.v2.patch > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushmitha Sreenivasan updated TEZ-3433: --- Attachment: TEZ-3433.v2.patch > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.v2.patch > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushmitha Sreenivasan updated TEZ-3433: --- Attachment: (was: TEZ-3433.patch.1) > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.v2.patch > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushmitha Sreenivasan updated TEZ-3433: --- Attachment: TEZ-3433.v2.patch > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.v2.patch > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TEZ-3433) Tez UI: Searching using wrong ID causes error in all DAGs page
[ https://issues.apache.org/jira/browse/TEZ-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushmitha Sreenivasan updated TEZ-3433: --- Attachment: TEZ-3433.patch.1 [~Sreenath]: Addressed all the comments. Can you please take a look when you get a chance? Thanks. > Tez UI: Searching using wrong ID causes error in all DAGs page > -- > > Key: TEZ-3433 > URL: https://issues.apache.org/jira/browse/TEZ-3433 > Project: Apache Tez > Issue Type: Bug >Reporter: Sreenath Somarajapuram >Assignee: Sushmitha Sreenivasan > Attachments: TEZ-3433.patch, TEZ-3433.patch.1 > > > - In All DAGs page, DAG id uses an implementation separate from other search > parameters. > - It throws error on trying to search with a wrong ID. > - Fix the UI to display a "No records available!" message, similar to the one > we display on giving a wrong value in other fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
