> 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-transformation-steps-reference-overview/s3-csv-input-cp/options-s3-csv-input.md).
# Options
**CAUTION:**
For technical reasons, parallel reading of S3 files is only supported on files that do not have fields with line breaks or carriage returns in them.
The following options are available for the S3 CSV Input transformation step.
| Option | Description |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Step name** | Specify the unique name of the S3 CSV Input step on the canvas. You can customize the name or leave it as the default. |
| **S3 Bucket** | Specify the S3 container where the CSV object file is stored. Or click **Select bucket** to browse to and select the S3 container where the CSV object file is stored. |
| **Filename** | Specify one of the following names (or click Browse) for the input file:- The name (Filename) of the S3 source file.
- The field which will become the name of the S3 source file or files at runtime, if the S3 CSV Input step receives data from another step.
The file name of a file in the S3 Cloud uses the following schema:
s3n://s3\_bucket\_name/absolute\_path\_to\_file
|
| **Delimiter** | Specify the file delimiter character used in the source file. The default delimiter for the CSV File Input step is a semicolon (;).
Click Insert Tab to use a tab as the delimiter.
Special characters can be set with the format: $\[value]
For example: $\[01] or $\[6F,FF,00,1F]
|
| **Enclosure** | Specify the enclosure character used in the source file. The default value is double quotes (“).
Special characters can be set with the format: $\[value]
For example: $\[01] or $\[6F,FF,00,1F]
|
| **Max line size** | Specify the maximum characters to be read per line by the input operation. The default is 5000. |
| **Lazy conversion?** | Select this option to delay the conversion of a row of data until it is absolutely necessary. |
| **Header row present?** | Select to indicate whether the source file contains a header row with column names. |
| **The row number field name** | Specify the name of the field that will contain the row number in the output of this step. |
| **Running in parallel** | Select to indicate whether you will have multiple instances of this step running (step copies) and if you want each instance to read a separate part of the S3 file(s).
When reading multiple files, the total size of all files is taken into consideration to split the workload. In that specific case, make sure that ALL step copies receive all files that need to be read; otherwise, the parallel algorithm will not work correctly.
|
---
# 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-transformation-steps-reference-overview/s3-csv-input-cp/options-s3-csv-input.md?ask=&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.