> 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/catalog-input/general-catalog-input/fields-tab-catalog-input/parquet-fields-catalog-input.md).

# Parquet fields

When Parquet data is read, the table defines the fields to read as input from the Parquet file.

![Parquet fields](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-293c0d0d7c45ad2feb7d6f01ba881c75e14a8b77%2FPDI_CatalogInput_Fields_Parquet.png?alt=media)

Enter the information for the Catalog Input step fields, as shown in the following table.

| Column                  | Description                                                                                                                                                                                 |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Path**                | The name of the field as it appears in the Parquet data file, and the Parquet data type. An associated PDI field type is provided in parentheses.                                           |
| **Name**                | The name of the input field.                                                                                                                                                                |
| **Type**                | The type of the input field as detected by PDI.                                                                                                                                             |
| **Format**              | Specify the [Date formats](/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/common-formats/date-formats.md) when the **Type** specified is **Date**. |
| **Get Fields** (button) | Click to retrieve a list of fields derived from the source file in Data Catalog.                                                                                                            |

Provide a path to a Parquet data file and click **Get Fields**. When the fields are retrieved, the Parquet type is converted to an applicable PDI type, as shown in the [PDI types](/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/catalog-input/general-catalog-input/fields-tab-catalog-input/parquet-fields-catalog-input/pdi-types.md) table. You can change the type by using the **Type** drop-down menu or by entering the type manually.


---

# 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/catalog-input/general-catalog-input/fields-tab-catalog-input/parquet-fields-catalog-input.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.