Join Slack
Powered by
<#1667 break: Require SQLAlchemy 2.0 for SQL taps ...
# meltano-repo-activity
g
GitHub
06/24/2025, 9:22 PM
#1667 break: Require SQLAlchemy 2.0 for SQL taps and targets
Issue created by
edgarrmondragon
### Feature scope Taps (catalog, state, stream maps, etc.) ### Description We should require new taps and targets use SQLAlchemy 2.0 to avoid having to migrate them later, and come up with a migration plan for existing ones. Most of the compatibility work was done in
#1357
, but individual connectors may still be using deprecated APIs. #### Ecosystem Support • Athena:
PyAthena
supports SQLAlchemy 2.0 since
v3.0.0
. • BigQuery: The SQLAlchemy Dialect for BigQuery supports SQLAlchemy 2.0 since
v1.11.0
. • Clickhouse:
ClickHouse SQLAlchemy
supports SQLAlchemy 2.0 since
0.3.0
. • CockroachDB: The
CockroachDB dialect for SQLAlchemy
supports SQLAlchemy 2.0 since
v2.0.0
. • duckdb:
duckdb-engine
supports SQLAlchemy 2.0 since
v0.7.0-rc1
. • Redshift:
sqlalchemy-redshift
doesn't support it yet (
sqlalchemy-redshift/sqlalchemy-redshift#264
). • Snowflake:
Snowflake SQLAlchemy
supports SQLAlchemy 2.0 since
v1.6.1
. • Starrocks: SQAlchemy 2.0+ is supported since 1.1.0 (
StarRocks/starrocks@3b3a67f
) Related: •
MeltanoLabs/target-postgres#87
•
snowflakedb/snowflake-sqlalchemy#380
•
snowflakedb/snowflake-sqlalchemy#514
meltano/sdk
g
GitHub
06/24/2025, 9:22 PM
#1667 break: Require SQLAlchemy 2.0 for SQL taps and targets
Issue closed as completed by
edgarrmondragon
meltano/sdk
Open in Slack
Previous
Next