> 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/advanced-topics-pentaho-data-integration-overview/using-pan-and-kitchen-with-a-hadoop-cluster/using-the-pdi-client.md).

# Using the PDI client

Perform the following steps to configure the PDI client host machine to run jobs or transformations from the command line interface (CLI).

1. Create a connection to the Hadoop cluster where you want to run your job or transformation.
2. Create and test the job or transformation in the PDI client to verify it works as expected.
3. Navigate to the `design-tools/data-integration/plugins/pentaho-big-data-plugin` directory and open the `plugin.properties` file with any text editor.
4. Set the value of the *hadoop.configurations.path* property to the location of the `metastore` directory, such as `hadoop.configurations.path=/home/<user>/.pentaho`.

   The `metastore` directory is created when you set up a named connection to the Hadoop cluster. The default metastore location for the PDI client is `home/<user>/.pentaho/metastore`.
5. 5. Save and close the `plugin.properties` file.


---

# 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/10.2-data-integration/advanced-topics-pentaho-data-integration-overview/using-pan-and-kitchen-with-a-hadoop-cluster/using-the-pdi-client.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.