wiktor2200 commented on issue #20863: URL: https://github.com/apache/superset/issues/20863#issuecomment-1195626217
I've fixed it. The problem was caused by external source (releasing of `snowflake-connector-python` ver. `2.7.10` https://github.com/snowflakedb/snowflake-connector-python/releases today). For Superset <-> Snowflake `snowflake-sqlalchemy 1.2.4` python package is used, which is quite old now (but it's only one version supported by Superset): https://superset.apache.org/docs/databases/snowflake/#snowflake and they are working on migration to new one. Even having package version hardcoded: `snowflake-sqlalchemy==1.2.4` in helm definitions didn't help. Becuase `snowflake-sqlalchemy` package has requirements defined in python script here: `snowflake-connector-python<3.0.0`: https://github.com/snowflakedb/snowflake-sqlalchemy/blob/666843d320315d2fd2b5c4129b929af20669008d/setup.py#L36, so it's downloading the newest `2.7.10` version anyways (fulfilling the condiition `<3.0.0`), but this version is not compatible with `snowflake-sqlalchemy==1.2.4` and requires additional package: `typing-extensions>=4.3.0`. So the fix here was to force install previous version of `snowflake-connector-python==2.7.9` (which still `<3.0.0`), as well as `typing-extensions>=4.3.0` so all requirements were fulfilled and `snowflake-sqlalchemy==1.2.4` doesn't download newest incompatible version. ``` typing-extensions>=4.3.0 snowflake-connector-python==2.7.9 snowflake-sqlalchemy==1.2.4 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
