aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Shirchenko (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AURORA-1733) Introduce a TaskHistory struct to TaskQuery to support limiting number of taskEvents per instance
Date Tue, 12 Jul 2016 21:01:20 GMT
Dmitriy Shirchenko created AURORA-1733:
------------------------------------------

             Summary: Introduce a TaskHistory struct to TaskQuery to support limiting number
of taskEvents per instance
                 Key: AURORA-1733
                 URL: https://issues.apache.org/jira/browse/AURORA-1733
             Project: Aurora
          Issue Type: Story
            Reporter: Dmitriy Shirchenko
            Assignee: Maxim Khutornenko


Our use case is to pull back latest task state history but we only want to pull back a specific
number of events per instance (usually 1). We have not been able to find a way to do that.

Right now we use TaskQuery with getTasksWithoutConfigs with a TaskQuery that pulls back everything
in a healthy state (includes ASSIGNED, RUNNING) to display to our users on our internal UI.
This has become too big of a blob to process.

Proposal is to introduce and implement the following:
{code}
struct TaskHistory {
0: set<ScheduleStatus> statuses
1: i32 limit
}
{code}

and add it to TaskQuery

{code}
struct TaskQuery {
...
15: TaskHistory taskHistory
}
{code}

This is an alternative iteration on proposal in AURORA-1722 and are related tasks. 

Comments?




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

Mime
View raw message