> 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-input/options-reuse/source-tab-kettle-engine/embedded-schema-kettle-engine.md).

# Embedded schema

![Avro Input Embedded Schema dialog](/files/PSXlNEBL8xIPOpduTt6G)

If you select Avro file as your **Format**, the Avro Input step assumes the schema is embedded with your data. The location of the source can be either a file or a PDI field.

| Option     | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Source** | <p>Specify the location of the source data and embedded schema:</p><ul><li><strong>From file</strong>: Specify the <strong>Folder/File name</strong> of the file or a folder containing multiple files, which is the fully qualified URL of the source file name. You can also click <strong>Browse</strong> to navigate to the source file or folder through your VFS connection. See <a href="/pages/U66nnANI85sI19SI8pKW">Connecting to Virtual File Systems</a> for more information. A single Avro file is specified to read as input.</li><li><strong>From field</strong>: Select the <strong>Field name</strong>containing the location of your source. The list of available fields comes from any PDI step connected to the Avro Input step.</li></ul> |


---

# 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-input/options-reuse/source-tab-kettle-engine/embedded-schema-kettle-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.