[
https://issues.apache.org/jira/browse/TEZ-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343443#comment-14343443
]
Prakash Ramachandran commented on TEZ-1652:
-------------------------------------------
[~jeagles] agree that its better to keep a different model of task_attempt for
swimlane.
was also wondering if it makes sense to download tasks on a vertex basis - for
ex check the vertex start/end time to see which vertexes have tasks which fall
in the timeline currently visible. on scroll we can download tasks belonging to
other vertexes when they come into the timeline visible.
> 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)
