> 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-transformation-steps-reference-overview/mapreduce-output.md).

# MapReduce Output

This step defines the key/value pairs for Hadoop output. The output of this step becomes the Hadoop output, and depends on how you have configured the transformation. This step may be included in a transformation used as a Mapper, Combiner, or Reducer.

When this step is included in a **Mapper** transformation type, and a combiner and/or reducer is configured, the output will be the input pairs for the combiner and/or the reducer. If no combiner or reducers are configured, the output is passed with the submitting Hadoop job’s format.

When this step is included in a **Combiner** transformation type, and a reducer is configured, the output will be the input pairs for the reducer. If no reducer is configured, the output is passed with the submitting Hadoop job’s format.

When this step is included in a **Reducer** transformation type, then the output is passed with the submitting Hadoop job’s format. The data type for the keys or values must be defined before this step.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/mapreduce-output.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
