You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Shubham (Jira)" <ji...@apache.org> on 2020/03/02 10:05:00 UTC
[jira] [Updated] (OOZIE-3434) Filtering for invalid jobtype should
give error message
[ https://issues.apache.org/jira/browse/OOZIE-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shubham updated OOZIE-3434:
---------------------------
Attachment: OOZIE-3434-001.patch
> Filtering for invalid jobtype should give error message
> -------------------------------------------------------
>
> Key: OOZIE-3434
> URL: https://issues.apache.org/jira/browse/OOZIE-3434
> Project: Oozie
> Issue Type: Bug
> Reporter: Andras Salamon
> Assignee: Shubham
> Priority: Minor
> Attachments: OOZIE-3434-001.patch
>
>
> It is possible for specifying the jobtype during jobs filter in the REST API and in the command line as well. Supported jobtypes are: {{wf}}, {{coord}}, {{bundle}}
> If we filter for an invalid jobtype then the command line version does not print anything:
> {noformat}$ oozie jobs -jobtype xxx
> {noformat}
> The REST api gives a JSON containing a NullPointerException:
> {noformat}/ 20190219121114
> // http://localhost:11000/oozie/v1/jobs?jobtype=xxx
> {
> "errorMessage": "java.lang.NullPointerException",
> "httpStatusCode": 500
> }
> {noformat}
> We should give a meaningful error message in this case like {{unrecognized jobtype: xxx}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)