> 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/pdi-job-entries-reference-overview/hadoop-copy-files/options-hadoop-copy-files-job/settings-tab.md).

# Settings tab

![Settings tab, Hadoop Copy Files](https://2745965000-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvZoINBz5C5WnDZQlbOJQ%2Fuploads%2Fgit-blob-0d0d210170f6ee63e0701883b20c387ac0b857c6%2FPDI_JobEntry_HadoopCopyFiles_Settings.png?alt=media)

| Option                                 | Description                                                                                                       |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Include subfolders**                 | Select to copy all subdirectories in the chosen directory.                                                        |
| **Destination is a file**              | Select to specify the destination is a file.                                                                      |
| **Copy empty folders**                 | Select to copy empty directories. The **Include Subfolders** option must be selected for this option to be valid. |
| **Create destination folder**          | Select to create the specified destination directory if it does not exist.                                        |
| **Replace existing files**             | Select to overwrite duplicate files in the destination directory.                                                 |
| **Remove source files**                | Select to remove the source files after copying them. This is equivalent to a move procedure.                     |
| **Copy previous results to arguments** | Select to use previous step results as your sources and destinations.                                             |
| **Add files to result files name**     | Select to create a list of files that were copied in this step.                                                   |

If you are not using Kerberos security, this step sends the username of the logged-in user when copying the files regardless of the username entered in the connect field. To change the username, set the environment variable **HADOOP\_USER\_NAME** to the username you want to use. You can set the username by changing the **OPT** variable in the `spoon.bat` or `spoon.sh` file as shown in the following example:

```
OPT="$OPT .... -DHADOOP_USER_NAME=HadoopNameToSpoof"
```


---

# 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/pdi-job-entries-reference-overview/hadoop-copy-files/options-hadoop-copy-files-job/settings-tab.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.