You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm unable to create datasets in Superset from a Snowflake Database. However, I can query that same table in the SQL Lab with no issues (i.e., select * from cortex.daily_fact works as expected). This issue may not be reproducible locally (because this is a private snowflake instance). However, I was able to get the error locally by running:
git clone https://github.com/apache/superset && cd superset
root@806c33d8de11:/app# superset version
Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
2024-10-14 20:50:08,651:INFO:superset.utils.logging_configurator:logging was configured successfully
2024-10-14 20:50:08,654:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
/usr/local/lib/python3.10/site-packages/flask_limiter/extension.py:293: UserWarning: Using the in-memory storage for tracking rate limits as no storage was explicitly specified. This is not recommended for production use. See: https://flask-limiter.readthedocs.io#configuring-a-storage-backend for documentation about configuring the storage backend.
warnings.warn(
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Superset 4.0.2
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
The text was updated successfully, but these errors were encountered:
I found a similar closed issue regarding a database driver error when connecting with Snowflake from Superset. The suggested solution was to use the connection string format snowflake://{user}:{password}@{account}.{region}/{database} by dropping the parts after '?' [1].
In your case, the error message 'NullType' object is not callable suggests that there might be an issue with how the Snowflake data types are being mapped to SQLAlchemy types. This could be related to the snowflake-sqlalchemy library's handling of nullable columns, which might be causing a NullType object to be incorrectly instantiated.
You might want to check if there are any updates or patches for the snowflake-sqlalchemy library that address this issue. Additionally, reviewing the data type mappings and ensuring that the Snowflake columns are correctly defined and compatible with SQLAlchemy could help resolve the problem.
Per the dosubot's recommendation, I tried connecting to Snowflake with a URI connection string, and I'm still getting the same error when attempting to create the Dataset.
Bug description
I'm unable to create datasets in Superset from a Snowflake Database. However, I can query that same table in the
SQL Lab
with no issues (i.e.,select * from cortex.daily_fact
works as expected). This issue may not be reproducible locally (because this is a private snowflake instance). However, I was able to get the error locally by running:git clone https://github.com/apache/superset && cd superset
echo "snowflake-sqlalchemy" >> ./docker/requirements-local.txt
docker compose -f docker-compose-image-tag.yml up --build
Datasets
>>+ Dataset
Screenshots/recordings
Superset version
4.0.2
Python version
3.10
Node version
Not applicable
Browser
Safari
Additional context
Error in Logs
Versions
snowflake-sqlalchemy
superset
Checklist
The text was updated successfully, but these errors were encountered: