> For the complete documentation index, see [llms.txt](https://docs.omnata.com/omnata-product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/databricks/release-history.md).

# Release History

***

### V2.0

#### Created: 2026-05-27

* Added support for the new connection flow

***

### V1.2

#### Created: 2026-04-25

* implement SQL WHERE clause validation to prevent injection attacks
* ensured queries are only logged into the event tables if we are in debug mode

***

### V1.1

#### Created: 2026-03-26

* fixed issue with timestamp being used as a cursor field which would cause issues
* ensured correct datatype mappings between Databricks and JSON
* ensured descriptions are added to the schema and uses the column name if the description from databricks is missing
* added a proc which will create a new network rule which can be used in connection setups for PrivateLink connections

***

### V1.0

#### Created: 2026-03-15

* initial version covering off inbound high watermark

***


---

# 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.omnata.com/omnata-product-documentation/omnata-sync-for-snowflake/apps/databricks/release-history.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.