> 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/schema-tab-pentaho-engine.md).

# Schema tab

![Avro Output Schema tab](/files/HyTBZjq8ho2czp8UWcVn)

The following options in the **Schema** tab define how the [Avro schema](https://avro.apache.org/docs/1.8.1/spec.html#schema_record) file will be created:

| Option          | Description                                                                                                                                                                                                                                                                                                                                                                                                        |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **File name**   | Specify the fully qualified URL where the Avro schema file will be written. The URL may be in a different format depending on file system type. You can also click **Browse** to navigate to the schema file on your file system. If a schema file already exists, it will be overwritten. If you do not specify a separate schema file for your output, PDI will write an embedded schema in your Avro data file. |
| **Namespace**   | Specify the name, together with the **Record name** field, that defines the "full name" of the schema (`example.avro` for example).                                                                                                                                                                                                                                                                                |
| **Record name** | Specify the name of the Avro record (`User` for example).                                                                                                                                                                                                                                                                                                                                                          |
| **Doc value**   | Specify the documentation provided for the schema.                                                                                                                                                                                                                                                                                                                                                                 |


---

# 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/schema-tab-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.