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

Prakash Ramachandran commented on TEZ-2780:
-------------------------------------------

[~Sreenath] still reviewing the changes, one quick question though. Why does 
the polling class need to be a mixin? this has two disadvantages.
1. there can be only a single instance of the polling. 
2. its tied to the type of controller it is used in. 
IMHO it would be better if its not a mixin, instantiate it in init. and 
depending on if polling is required, do a start/stop. if you are concerned 
about code reuse across task/task attempts write a helper function that takes 
in the required arguments. 

> Tez UI: Update All Tasks page while in progress.
> ------------------------------------------------
>
>                 Key: TEZ-2780
>                 URL: https://issues.apache.org/jira/browse/TEZ-2780
>             Project: Apache Tez
>          Issue Type: Sub-task
>          Components: UI
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>         Attachments: TEZ-2780.1.patch, TEZ-2780.wip.1.patch
>
>
> Add AM API for fetching realtime tasks info:
> - API endpoint : /ws/v2/tez/tasksInfo
> - Query Params:
> -- dagID: The complete dagID, (mandatory).
> -- vertexMinID: A comma separated list. vertexMinID = vertexIndex.
> -- taskMinID: A comma separated list. taskMinID = vertexIndex_taskIndex
> -- limit: Maximum number of items to be returned (Defaults to 100).
> - If taskMinID is passed: All (capped by limit) the specified tasks will be 
> returned. vertexMinID if present wont be considered.
> - IF vertexMinID is passed: All (capped by limit) tasks under the vertices 
> will be returned.
> - If just dagID is passed: All (capped by limit) tasks under the DAG will be 
> returned.
> - Data returned: complete task id, progress, status
> Modify table component to automatically update cell based on model change.



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

Reply via email to