[
https://issues.apache.org/jira/browse/TEZ-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342990#comment-14342990
]
Sreenath Somarajapuram commented on TEZ-1652:
---------------------------------------------
Hi [~jeagles],
Please help to understand the purpose of SwimlaneTaskAttempt model. Wouldn't
TaskAttempt model do the same job?
Also would be awesome if we can have a design doc for swimlane. This was
created for Dag View
https://docs.google.com/a/hortonworks.com/document/d/1FT1F103RrnzOdA-mEo6bU-YS_QmIlT1XmWdueD3Hk8o,
guess something similar would help to understand the UI that we are targeting
for.
> Large job support for Swimlane view
> -----------------------------------
>
> Key: TEZ-1652
> URL: https://issues.apache.org/jira/browse/TEZ-1652
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-1652-v1.patch, TEZ-1652.1.patch, TEZ-1652.2.patch
>
>
> Issue is that by default, Timeline Server only returns 100 max entity results
> per query. For query for all task attempts for dag. A limit should be high
> enough to get all entries and yet provide responsiveness.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
