> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-job-entries-reference-overview/pentaho-mapreduce/options-pentaho-mapreduce-job/job-setup-tab.md).

# Job Setup tab

![Job Setup tab, Pentaho MapReduce](/files/Groy4Nks9rGE6fjGJGJp)

The following table describes the options for setting up the inputs and outputs of the job:

| Option                            | Definition                                                                                                                                                                                                                                                               |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Input path**                    | Enter the path of the input directory, such as `/wordcount/input`, from your Hadoop cluster where the source data for the MapReduce job is stored. A comma-separated list can be used for multiple input directories.                                                    |
| **Output path**                   | <p>Enter the path of the directory, such as <code>/wordcount/output</code>, on your Hadoop cluster where you want the output from the MapReduce job to be stored.</p><p><strong>Note:</strong> The output directory cannot exist prior to running the MapReduce job.</p> |
| **Remove output path before job** | Select to remove the specified output path before the MapReduce job is scheduled.                                                                                                                                                                                        |
| **Input format**                  | Enter the Apache Hadoop class name that describes the input specification for the MapReduce job. See [InputFormat](http://hadoop.apache.org/docs/stable/api/index.html?org/apache/hadoop/mapreduce/lib/input/FileInputFormat.html) for more information.                 |
| **Output format**                 | Enter the Apache Hadoop class name that describes the output specification for the MapReduce job. See [OutputFormat](http://hadoop.apache.org/docs/stable/api/index.html?org/apache/hadoop/mapreduce/lib/output/FileOutputFormat.html)for more information.              |
| **Ignore output of map key**      | Select to ignore the key output from the mapper transformation and replace it with `NullWritable`.                                                                                                                                                                       |
| **Ignore output of map value**    | Select to ignore the value output from the mapper transformation and replace it with `NullWritable`.                                                                                                                                                                     |
| **Ignore output of reduce key**   | Select to ignore the key output from the combiner and/or reducer transformations and replace them with `NullWritable`. This requires a reducer transformation to be used, not the Identity Reducer.                                                                      |
| **Ignore output of reduce value** | Select to ignore the key output from the combiner and/or reducer transformations and replace them with `NullWritable`. This requires a reducer transformation to be used, not the Identity Reducer.                                                                      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-job-entries-reference-overview/pentaho-mapreduce/options-pentaho-mapreduce-job/job-setup-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.