[
https://issues.apache.org/jira/browse/OOZIE-2461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266354#comment-15266354
]
abhishek bafna commented on OOZIE-2461:
---------------------------------------
Both the FILTERs needs to be registered with FILTER_NAMES array into the
_CoordinatorEngine_ and _JobsFilterUtils_ to work with coordinators and bundles
respectively.
{code}
public static final String FILTER_LAST_MODIFIED_TIME_START =
"startlastmodifiedtime";
public static final String FILTER_LAST_MODIFIED_TIME_END =
"endlastmodifiedtime";
{code}
> Workflow, Coordinator and Bundle job querying should have last modified filter
> ------------------------------------------------------------------------------
>
> Key: OOZIE-2461
> URL: https://issues.apache.org/jira/browse/OOZIE-2461
> Project: Oozie
> Issue Type: Bug
> Reporter: Satish Subhashrao Saley
> Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2461-1.patch, OOZIE-2461-6.patch,
> OOZIE-2461-7.patch, OOZIE-2461-8.patch
>
>
> To get currently running coordinator and id, one user had to do
> http://localhost:11000/oozie/v1/jobs?jobtype=coord&filter=user%3satish_1.0%3B&offset=1&len=3000
> They could not use name in the filter as they include a version and keep
> changing. For eg:
> urs_satish_filter-0.1-daily-coord
> urs_puru_service-0.4-hourly-coord
> It would be good to have last modified filter to get recently active
> coordinators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
