GitHub user shermanLF added a comment to the discussion: Issues to execute
queries via SQL Lab
A misconfigured RESULT_CACHE fails in a non-obvious way. There are no
exceptions logged related to the RESULT_CACHE.
The fix is to have a working RESULT_CACHE.
Superset needs to do a better job indicating there are problems with the
RESULT_CACHE and other caches.
**My journey**
**The Superset environment**
- Superset in an ECS task
- AWS Redis Elasticache
- AWS PostgreSQL for Superset database and data sources.
**Set up**
- The connection of Superset to its own database working, which uses SQLAlchemy
like SQL Lab.
- Creating the database connections through the Superset UI works - either with
the dialog or manually putting in a SQLAlchemy URI.
- Connections pass validation.
- Charts in Superset can be created based on the data source.
**SQL Lab problem**
- Browsing the metadata of a database works.
- Running a query in the Lab fails.
**Error**
```
PostgreSQL Error
Invalid input of type: 'set'. Convert to a bytes, string, int or float first.
```
>From the activity log:
`{"source": "sqlLab", "source_id": "6", "db_id": 5, "schema": "public", "ts":
1746105365220, "event_name": "sqllab_fetch_failed_query", "has_err": true,
"start_offset": 1746105364455, "error_type": "GENERIC_DB_ENGINE_ERROR",
"error_details": "Issue 1002 - The database returned an unexpected error.",
"event_type": "timing", "trigger_event": "L-QKeFkiCxhWmH2RF5xg9"}`
**Result**
Of course this looks like a database related issue :-(
Queue days of database log and configuration analysis.
I changed the RESULT_CACHE to use a database backend rather than Redis
Elasticache, and the SQL Lab error disappears.
GitHub link:
https://github.com/apache/superset/discussions/26784#discussioncomment-13013568
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
