> 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/10.2-data-integration/data-integration-perspective-in-the-pdi-client/advanced-topics-pdi-perspective/pdi-run-modifiers/variables/kettle-variables/set-kettle-or-java-environment-variables-in-the-pentaho-mapreduce-job-entry.md).

# Set Kettle or Java environment variables in the Pentaho MapReduce job entry

Pentaho MapReduce jobs are typically run in distributed fashion, with the mapper, combiner, and reducer run on different nodes. If you need to set a Java or Kettle environment variable for the different nodes, such as the**KETTLE\_MAX\_JOB\_TRACKER\_SIZE**, set them in the Pentaho MapReduce job entry window.

**Note:** Values for Kettle environment variables set in the Pentaho MapReduce window override the Kettle environment variable values in the `kettle.properties` file.

To set kettle or java environment variables, complete these steps:

1. In the PDI client, double-click the Pentaho MapReduce job entry, then click the **User Defined** tab.
2. In the **Name** field, set the environment or Kettle variable you need:
   * For Kettle environment variables, type the name of the variable in the **Name** field, like this: `KETTLE_SAMPLE_VAR.`
   * For Java environment variables, preface the value with the `java.system.` prefix, like this: `java.system.SAMPLE_PATH_VAR.`
3. Enter the value of the variable in the **Value** field.
4. Click the **OK** button.


---

# 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/10.2-data-integration/data-integration-perspective-in-the-pdi-client/advanced-topics-pdi-perspective/pdi-run-modifiers/variables/kettle-variables/set-kettle-or-java-environment-variables-in-the-pentaho-mapreduce-job-entry.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.