[OOZIE-1227] In a coordinator, specifying the <app-path> without a namenode causes it to fail

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.0
• Fix Version/s: 3.3.2
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 15/Feb/13 05:03
• Updated: 20/Jul/13 00:03
• Resolved: 15/Feb/13 07:05

Description

In a coordinator, some users don't specify the name node in the path to the workflow application. e.g.

<action>
    <workflow>
        <app-path>/user/${coord:user()}/${examplesRoot}/apps/aggregator</app-path>
        ...

This now causes the coordinator to fail. I think this may also affect other paths because many of them go through the HadoopAccessorService.

Ideally, we should fix this behavior to the old way: have it default to HDFS and get the namenode automatically if no scheme://host:port is given.

A workaround is to to add the following property to oozie-site.xml

<property>
    <name>oozie.service.HadoopAccessorService.supported.filesystems</name>
    <value>*</value>
</property>

This causes Oozie to effectively have the old behavior. The downside of this workaround is that administrators cannot restrict the filesystems that Oozie will allow (* means all filesystems, even non-real ones).

Instead of making users use that workaround, we can simply make Oozie skip the check if the scheme is null. It would allow the old behavior without disabling the scheme check.