> 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/avro-output/options-avro-output-reuse/fields-tab-avro-output-pentaho-engine.md).

# Fields tab

![Avro Output Fields tab](/files/Gb5fxVgDEYM1xQfHfsTc)

**Note:** The table in the **Fields** tab defines the following fields that make up the Avro schema created by this step:

| Field             | Description                                                                                            |
| ----------------- | ------------------------------------------------------------------------------------------------------ |
| **Avro path**     | The name of the field as it will appear in the Avro data and schema files.                             |
| **Name**          | The name of the PDI field.                                                                             |
| **Avro type**     | Defines the Avro data type of the field.                                                               |
| **Precision**     | Applies only to the Decimal Avro type, the total number of digits in the number. The default is 10.    |
| **Scale**         | Applies only to the Decimal Avro type, the number of digits after the decimal point. The default is 0. |
| **Default value** | The default value of the field if it is null or empty.                                                 |
| **Null**          | Specify if the field can contain null values.                                                          |

**Note:** To avoid a transformation failure, make sure the **Default value** field contains values for all fields where **Null** is set to No.

**Note:** As shown in the table below, you can click **Get Fields** to populate the fields from the incoming PDI stream or these fields can be defined manually. During the retrieval of fields, a PDI type is converted to an appropriate Avro type. If desired, you can change the converted field type to another Avro type.

| PDI Type        | Avro Type |
| --------------- | --------- |
| **InetAddress** | String    |
| **String**      | String    |
| **TimeStamp**   | TimeStamp |
| **Binary**      | Bytes     |
| **BigNumber**   | Decimal   |
| **Boolean**     | Boolean   |
| **Date**        | Date      |
| **Integer**     | Long      |
| **Number**      | Double    |


---

# 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/pdi-transformation-steps-reference-overview/avro-output/options-avro-output-reuse/fields-tab-avro-output-pentaho-engine.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.