[
https://issues.apache.org/jira/browse/OOZIE-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Azrael updated OOZIE-1779:
--------------------------
Attachment: OOZIE-1779.2.patch
Updated patch include:
* Fix test failure
* Make filter name rule for WF, COORD, BUNDLE to be consistent : throw
exception if upper case
Currently if filter name is not lower case, WF and BUNDLE throw exception.
However in COORD, the upper case filter name is OK even though the
{{TestCoordinatorEngineSimple.testParseFilterNegative}} passed.
Here is as is:
{code}
$ oozie jobs -filter='sTaTus=SUCCEEDED'
Error: E0420 : E0420: Invalid jobs filter [sTaTus=SUCCEEDED;], invalid name
[sTaTus]
$ oozie jobs -jobtype=coord -filter='sTaTus=SUCCEEDED'
OK
$ oozie jobs -jobtype=bundle -filter='sTaTus=SUCCEEDED'
Error: E0420 : E0420: Invalid jobs filter [sTaTus=SUCCEEDED;], invalid name
[sTaTus]
{code}
Manual test for {{FreQuency}}. It expect CoordinatorEngineException.
{code}
$ oozie jobs -jobtype=coord -filter='FreQuency=1;UniT=minutes'
OK
{code}
> Add parent-id as a filter option
> --------------------------------
>
> Key: OOZIE-1779
> URL: https://issues.apache.org/jira/browse/OOZIE-1779
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Azrael
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1779.1.patch, OOZIE-1779.2.patch
>
>
> Currently filtering options on jobs list are
> name, user, group, status, frequency and time-unit.
> With increasing usage of coordinators and bundles, adding parent-id should be
> useful instead of always searching top-down from parent to child.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
