[
https://issues.apache.org/jira/browse/OOZIE-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated OOZIE-39:
------------------------------------
Fix Version/s: pre-Apache
> Oozie example docs may be unclear on the placements of the job.properties file
> ------------------------------------------------------------------------------
>
> Key: OOZIE-39
> URL: https://issues.apache.org/jira/browse/OOZIE-39
> Project: Oozie
> Issue Type: Improvement
> Reporter: Harsh J
> Priority: Trivial
> Labels: doc
> Fix For: pre-Apache
>
> Attachments: OOZIE-39.r1.diff
>
> Original Estimate: 2m
> Remaining Estimate: 2m
>
> The 'Running the Example' docs go as:
> {code}
> 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.
> {code}
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
