[jira] [Comment Edited] (TEZ-2346) TEZ-UI: Lazy load other info / counter data

["Jonathan Eagles (JIRA)" <ji...@apache.org>]

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

Jonathan Eagles edited comment on TEZ-2346 at 11/16/15 4:54 AM:
----------------------------------------------------------------

Ok. I've been playing around with this to get a better understanding. This is almost ready to go in. We just need to fix log handling and giving the user a slow warning. We are very wisely not calling tez_app (the app config in the otherinfo as well) rest APIs if we can find the app in the generic application history server. One thing that isn't happening correctly is regards to logs.

*Logs Handling*
logs link is not getting populated anymore (contained the other info section)
logs are not getting merged in when the other info is retrieved
I think that logs should not show by default on the dags index (possibly remove this field)
if they are selected then the otherinfo should be retrieved

*Slow Notice*
I want to be enable the user to be able to know that selecting column that triggers otherinfo retrieval could potentially slow. Is there a way (perhaps in the column selector there could be a "slow warning" or there could be an optimized select button)

If the two above issues could be fixed, this can be committed. It is such a better user experience for me personally. Thank you for your continued work on this.

In the future, we could start retrieving the log url from the generic application history. but that is a separate jira.
_ws/v1/applicationhistory/apps/application_1446839987226_32911/appattempts_



was (Author: jeagles):
Ok. I've been playing around with this to get a better understanding. This is almost ready to go in. We are very wisely not calling tez_app (the app config in the otherinfo as well) rest APIs if we can find the app in the generic application history server. One thing that isn't happening correctly is regards to logs.

logs link is not getting populated anymore (contained the other info section)
logs are not getting merged in when the other info is retrieved
I think that logs should not show by default on the dags index (possibly remove this field)
if they are selected then the otherinfo should be retrieved

I want to be enable the user to be able to know that selecting column that triggers otherinfo retrieval could potentially slow. Is there a way (perhaps in the column selector there could be a "slow warning" or there could be an optimized select button)

Alternately, we could start retrieving the log url from the generic application history. but that is a separate jira.
_ws/v1/applicationhistory/apps/application_1446839987226_32911/appattempts_



> TEZ-UI: Lazy load other info / counter data
> -------------------------------------------
>
>                 Key: TEZ-2346
>                 URL: https://issues.apache.org/jira/browse/TEZ-2346
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>            Priority: Critical
>         Attachments: Screen-Shot-2015-04-21-at-1.56.28-AM.jpg, TEZ-2346.1.patch, TEZ-2346.2.patch, TEZ-2346.3.patch, TEZ-2346.4.patch, TEZ-2346.wip.1.patch
>
>




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