[OOZIE-39] Oozie example docs may be unclear on the placements of the job.properties file

• Type: Improvement
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: pre-Apache
• Labels: doc
• Assignee: Unassigned
• Reporter: Harsh J
• Created: 01/Sep/11 16:26
• Updated: 14/May/12 01:40
• Resolved: 08/Oct/11 17:42

Description

The 'Running the Example' docs go as:

Add Oozie bin/ to the environment PATH.

The examples assume the JobTracker is localhost:9001 and the NameNode is hdfs://localhost:9000 . If the actual values are different, the job properties files in the examples directory must be edited to the correct values.

The example applications are under the examples/app directory, one directory per example. The directory contains the application XML file (workflow, or worklfow and coordinator), the job.properties file to submit the job and any JAR files the example may need.

The inputs for all examples are in the examples/input-data/ directory.

The examples create output under the examples/output-data/${EXAMPLE_NAME} directory.

It isn't specified clearly, after the step of placing the examples in HDFS, that the job.properties file is actually something per-user, and is client-side as a local file and not something that needs to be a HDFS path. This could mislead users into initially thinking that the job.properties path provided to run an example would require to be on HDFS.

In any case, we could benefit by adding a docnote on explicitly stating that the job properties is a local file prepared by the user.