[ https://issues.apache.org/jira/browse/AURORA-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343046#comment-15343046 ]
Maxim Khutornenko commented on AURORA-1722: ------------------------------------------- The {{limit}} would specify the number of scheduled tasks returned. Every task will have all task events associated with it. In practice, there are just a few events issued per task lifetime, so this overhead should not be causing any data transfer issues as long as {{getTasksWithoutConfigs}} is used. > Add new field to TaskQuery to allow querying latest statuses grouped by > instance id > ----------------------------------------------------------------------------------- > > Key: AURORA-1722 > URL: https://issues.apache.org/jira/browse/AURORA-1722 > Project: Aurora > Issue Type: Task > Components: Scheduler > Affects Versions: 0.16.0 > Reporter: Igor Morozov > > Currently in order to get the status of all job instances both failed and > running one needs to issue a query for all task statuses, then group them by > instance id and sort by timestamp to get the lastest statuses per instance. > For tasks with a lot of churn that may cause unnecessary transferring huge > blobs of thrifts. > The proposal is to include new member into TaskQuery struct > struct TaskQuery { > ... > 14: i32 limit_per_instance > } -- This message was sent by Atlassian JIRA (v6.3.4#6332)