> 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.md).

# Source tab

![Avro Input step Source tab](https://2745965000-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvZoINBz5C5WnDZQlbOJQ%2Fuploads%2Fgit-blob-26e101d5505b7096adf7ff1f8c92b21a3468b142%2FPDI_AvroInput_SourceTab_PentahoEngine.png?alt=media)

Use the **Source** tab to specify the location of the source data and its related schema. The schema that defines the Avro data is either embedded or in a different location.

Use **Format** to select from one of the following formats:

* **Avro file**

  The source material is in a single location. The schema is embedded with the data.
* **JSON datum**

  The source material is in different locations. The data is contained in a JSON format, and the schema is separate from the data.
* **Binary datum**

  The source material is in different locations. The data is contained in a binary format, and the schema is separate from the data.
* **Avro file (use alternate schema)**

  The source material is in different locations. The schema is separate from the data.

The options presented in the **Source** tab depend on whether the schema is embedded with or separate from the data.


---

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