[jira] [Commented] (OOZIE-848) Bulk Monitoring API - Consolidated view of jobs

["Mona Chitnis (JIRA)" <ji...@apache.org>]

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

Mona Chitnis commented on OOZIE-848:
------------------------------------

Done mostly with first run implementation of the filters and the queries associated. Trying to get thoughts around the query structure, so please comment.

We are given bundle-name, coordinator-names and other filters on coord actions e.g. status and interval for created time

In order to avoid a JOIN on the DB side, the sequence of queries is

Get list of bundle ID where bundle.appName = bundle-name;
Get list of coordinator IDs where coordinator.appName IN (coordinator-names) and coordinator.bundleId = bundleID (from previous query)
finally,
Get list of coordinator actions where action.jobId IN (coordinator IDs from previous query) AND action.bundleId = bundleID AND action.status IN (...) ...

An additional column bundleId is added to coordinator action table for this query to work.

Now, resultSet will include a list of coordinator actions carrying only corresponding coordinator IDs and bundle IDs for each. Need to think about constructing a readable response object (top-down from bundle) for the user with these bottom-up results?
How can an efficient "ORDER BY" be implemented for this case?
                
> Bulk Monitoring API - Consolidated view of jobs
> -----------------------------------------------
>
>                 Key: OOZIE-848
>                 URL: https://issues.apache.org/jira/browse/OOZIE-848
>             Project: Oozie
>          Issue Type: New Feature
>          Components: bundle, coordinator, workflow
>    Affects Versions: trunk
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>         Attachments: API_design_choices.pdf, Design_draft_bulk_monitoring.pdf
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> This feature is to enable getting the status and statistics of all of the coordinators and coordinator actions matching a filter for a specific pipeline (bundle) so the user can quickly determine if there are problems and take corrective action.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira