> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/articles-1/data/schema-evolution.md).

# Schema Evolution

When a change occurs to the schema of your data source, Upsolver automatically detects the change during ingestion and dynamically applies it to the target. This process, known as schema evolution, handles modifications such as the addition or removal of a column or changes in data types. Schema evolution ensures that your data remains consistent and up-to-date without requiring manual intervention.

The behavior of schema evolution can vary depending on the target data platform. Learn more about how schema evolution is handled for each target:

* [Iceberg Schema Evolution](https://app.gitbook.com/o/-MAbbSZFb8587RMXqY1u/s/KpsWQIZ3OMa5ck6PLmO4/~/changes/5/data/schema-evolution/iceberg-schema-evolution)
* [Snowflake Schema Evolution](https://app.gitbook.com/o/-MAbbSZFb8587RMXqY1u/s/KpsWQIZ3OMa5ck6PLmO4/~/changes/5/data/schema-evolution/snowflake-schema-evolution/~/overview)
* [Redshift Schema Evolution](https://app.gitbook.com/o/-MAbbSZFb8587RMXqY1u/s/KpsWQIZ3OMa5ck6PLmO4/~/changes/5/data/schema-evolution/redshift-schema-evolution/~/overview)


---

# 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://upsolver.gitbook.io/content/articles-1/data/schema-evolution.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.