> For the complete documentation index, see [llms.txt](https://docs.zingg.ai/zingg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingg.ai/zingg/connect-your-data/connect-cloud-warehouses/connect-snowflake.md).

# Connect Snowflake

Connect Zingg to Snowflake as a data source using the Snowflake Spark connector. Available in all editions.

{% hint style="success" icon="right-long" %}
This `config` connects Zingg to Snowflake as a DATA SOURCE using Spark. Available in all editions.
{% endhint %}

{% hint style="warning" icon="right-long" %}
Snowflake as a COMPUTE ENGINE (native Snowflake run without Spark) is Enterprise only.\
[Talk to us about Enterprise](https://www.zingg.ai/company/contact/contact).
{% endhint %}

### Prerequisites

Snowflake as a data source requires two dependency JARs on the Spark classpath. Download from `Maven` and add to `zingg.conf.`

```bash
spark.jars = snowflake - jdbc - 3.13.19.jar, \
spark - snowflake_2 .12 - 2.10.0 - spark_3 .1.jar
```

For the full Zingg installation, cluster setup, and any additional dependency configuration required when connecting Spark to Snowflake, follow the [Snowflake Platform Guide](/zingg/platform-guides/platform-guide-for-snowflake.md).

### Python API

```python
from zingg.client import*
from zingg.pipes import*

snowflakePipe = SnowflakePipe("snowflakeInput")
snowflakePipe.addProperty("sfUrl", "rfa59271.snowflakecomputing.com")
snowflakePipe.addProperty("sfUser", "sonalgoyal")
snowflakePipe.addProperty("sfPassword", "ZZ")
snowflakePipe.addProperty("sfDatabase", "TEST")
snowflakePipe.addProperty("sfSchema", "PUBLIC")
snowflakePipe.addProperty("sfWarehouse", "COMPUTE_WH")
snowflakePipe.addProperty("dbtable", "FEBRL")
snowflakePipe.addProperty("application", "zingg_zingg")
args.setData(snowflakePipe)
```

### JSON Config

```json
{
  "data" : [ {
    "name" : "test",
    "format" : "net.snowflake.spark.snowflake",
    "props" : {
      "sfUrl" : "rfa59271.snowflakecomputing.com",
      "sfUser" : "sonalgoyal",
      "sfPassword" : "ZZ",
      "sfDatabase" : "TEST",
      "sfSchema" : "PUBLIC",
      "sfWarehouse" : "COMPUTE_WH",
      "dbtable" : "FEBRL",
      "application" : "zingg_zingg"
    }
  } ]
}
```

{% hint style="success" icon="right-long" %}

### Supported file formats

Snowflake as a data source connects to tables and views via the Snowflake Spark connector. File formats (CSV, Parquet) are handled by Snowflake internally before Zingg reads the data. No additional format config needed on this connector.
{% endhint %}


---

# 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.zingg.ai/zingg/connect-your-data/connect-cloud-warehouses/connect-snowflake.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.