Snowflake docs still use the name Snowflake. Snowpark Connect for Apache Spark exists and is documented.
Read
10 Nov 2026
What it does well
Per Snowflake documentation, Snowpark Connect runs existing PySpark DataFrame code against the Snowflake engine over Spark Connect, and batch jobs are submitted with the Snowpark Submit CLI (read 2026-11-10).
Per Snowflake documentation, Iceberg tables can keep data in customer-managed S3, GCS or Azure storage through external volumes and a catalog integration such as AWS Glue.
Where it is limited
Per Snowflake documentation, Snowpark Connect supports Apache Spark 3.5 only, and DayTimeIntervalType, YearMonthIntervalType and user-defined types are unsupported (read 2026-11-10).
On-demand credit prices on AWS US East (Northern Virginia) are $2.00 (Standard), $3.00 (Enterprise) and $4.00 (Business Critical) per the Snowflake Service Consumption Table effective 2026-11-09 (read 2026-11-10); the Snowflake pricing page itself renders by script.
Published prices and cost results
Fact
Source type
Source, read
Warehouses bill credits per second with a 60-second minimum on each start; each size step roughly doubles credits per hour (Small is 2 credits per hour, Medium is 4). Snowflake's Service Consumption Table (effective 2026-11-09) lists on-demand credits on AWS US East at $2.00 (Standard), $3.00 (Enterprise) and $4.00 (Business Critical).
Snowpark Connect for Apache Spark runs existing PySpark DataFrame code against the Snowflake engine over the Spark Connect protocol; there is no Spark cluster, all workloads run on a Snowflake warehouse. Batch jobs are submitted with the Snowpark Submit CLI.
Because Snowflake rather than Spark is the engine, there are semantic differences: DayTimeIntervalType, YearMonthIntervalType and user-defined types are unsupported, and ByteType, ShortType and IntegerType are returned as LongType. The docs list unsupported APIs for DataFrame and Dataset.
Docs say the Spark DataFrame and Spark SQL code can be reused with minimal migration or changes; the compatibility notes say Spark Connect defers plan resolution, which changes behavior versus Spark Classic.
Docs provide a separate Optimizing Snowpark Connect for Spark workloads section and a Troubleshooting section covering known limitations, so some job-level adjustment is expected after migration.
Snowpark Connect supports Apache Spark 3.5 only; workloads written for 3.4 and below or 4.0 and above are not supported and may produce protocol errors or missing API failures.
Snowflake supports Iceberg tables (Parquet) with data in customer-managed S3, GCS or Azure storage via external volumes, an external catalog integration such as AWS Glue, and Delta files read through Delta Direct; Hudi was not listed on the page.
Snowflake runs on AWS, Azure and Google Cloud; AWS regions include us-east-1, us-west-2, eu-west-1 and ca-central-1. Each account is hosted in a single region.
Credits per warehouse-hour by size, billed per second with a 60-second minimum, times a price per credit by edition, cloud and region.
XL warehouse = 16 credits per hour. 16 x 2 hours = 32 credits x $3.00 = $96.00.
$96.00
Includes warehouse credits for two hours of an XL standard warehouse at the Enterprise on-demand rate. Excludes storage, cloud services credits beyond the daily allowance, and data transfer. The table lists credits per hour for each size but not the vCPU or memory behind each size, so which size equals the reference workload is an assumption. For the same hours, the Standard edition ($2.00 per credit) gives $64.00 and Business Critical ($4.00) gives $128.00; a 2XL warehouse (32 credits per hour) doubles each figure. Snowflake runs SQL and Snowpark in its own engine, not Spark on EC2.
Searched for and none found on 10 Nov 2026
Published benchmark for Spark batch jobs on Snowpark Connect with method (searched: docs.snowflake.com/en/developer-guide/snowpark-connect/snowpark-connect-, docs.snowflake.com/en/developer-guide/snowpark-connect/snowpark-connect-)