falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Balu Vellanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-474) Add Bulk APIs to drive the dashboard needs
Date Tue, 26 Aug 2014 08:01:11 GMT

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

Balu Vellanki commented on FALCON-474:
--------------------------------------

[~shwethags] [~svenkat] - I have a question regarding Oozie bulk API. When OozieClient.getBulkInfo(String
filter, int start, int len) is called, do you happen to know if the results are sorted by
startScheduleTime? If yes, what is the sort order? 

For Bulk API, default filter on actionStatus is "KILLED,FAILED".  I think user would want
to see N latest instances irrespective of the actionStatus. So I plan to set actionStatus
filter to all possible statuses. Please comment on this approach. 




> Add Bulk APIs to drive the dashboard needs
> ------------------------------------------
>
>                 Key: FALCON-474
>                 URL: https://issues.apache.org/jira/browse/FALCON-474
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: webapp
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>            Assignee: Balu Vellanki
>              Labels: rest_api
>             Fix For: 0.6
>
>         Attachments: Falcon-Jira-474-v2.patch, Falcon-Jira-474-v3.patch, Falcon-Jira-474-v4.patch
>
>
> This needs to be thought through based on the UX requirements. A use case that Ambari
wanted was to list feeds with status for the last 7 instances for each feed as a summary view.
> This should also support the performance requirements needed by the dashbaord.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message