You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Abhishek Bafna (JIRA)" <ji...@apache.org> on 2017/05/08 08:40:04 UTC
[jira] [Updated] (OOZIE-2751) LocalOozieClient is missing methods
from OozieClient
[ https://issues.apache.org/jira/browse/OOZIE-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhishek Bafna updated OOZIE-2751:
----------------------------------
Attachment: OOZIE-2751-09.patch
> LocalOozieClient is missing methods from OozieClient
> ----------------------------------------------------
>
> Key: OOZIE-2751
> URL: https://issues.apache.org/jira/browse/OOZIE-2751
> Project: Oozie
> Issue Type: Bug
> Reporter: Robert Kanter
> Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2751-00.patch, OOZIE-2751-01.patch, OOZIE-2751-02.patch, OOZIE-2751-03.patch, OOZIE-2751-04.patch, OOZIE-2751-05.patch, OOZIE-2751-06.patch, OOZIE-2751-07.patch, OOZIE-2751-08.patch, OOZIE-2751-09.patch
>
>
> {{LocalOozieClient}} works by wrapping direct calls to {{DagEngine}} in the normal {{OozieClient}} methods instead of making REST calls to an Oozie Server. However, it currently doesn't override all methods, which means you hit the {{OozieClient}} implementation, which tries to make a REST call and will fail (because it's not setup for that). For example, {{getStatus(String jobId)}} isn't overridden, and doesn't work when used from {{LocalOozieClient}}.
> We should also create a test that verifies that all methods are overridden.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)