-
Notifications
You must be signed in to change notification settings - Fork 13.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting superset error: 'str' object has no attribute 'tzinfo' when using elasticsearch with superset:// #29574
Comments
@mudasirmirza Hello! I'm here to assist you with any issues you're facing. Let's work together to resolve the problem. The error Here are the steps to fix this issue:
By ensuring that your datetime objects have the |
Just to add to it. If I run the same query directly selecting "ElasticSearch" as the data source and selecting the "Index"
This query returns proper results. |
Hello, were you able to solve the above issue? I am also running into the same problem when trying to get elasticsearch table data using superset meta db. The query works fine when using "ElasticSearch" as a datasource. Let me know if you were able to solve it and how? |
Hi @hardikjain178 , I was unable to resolve this and because of this I just dropped working on this. |
Bug description
I have added 2 data source. One ElaticSearch (named as es) and one MySQL (named as mysql).
I have enabled the "querying across database" feature using the feature FLAG as described in "https://superset.apache.org/docs/configuration/databases/#querying-across-databases" and named the meta db as "superset_meta"
Now when I go to sqllab and select "superset_meta" and then a simple query like below
I get below error
And in the docker-compose logs, I see below
In the logs, I can clearly see that it fetched the data but for some reason it is trying to find
tzinfo
in the fetchedjson
from the elasticsearch data source.Also in the logs, when it stared to process this query, it made a call like below
And after this I see the log showing the fetched columns.
I am not sure why is it still trying to look for
tzinfo
.Please let me know if any more information is required from my side related to this issue.
How to reproduce the bug
ENABLE_SUPERSET_META_DB
insuperset_config.py
elasticsearch-dbapi
indocker/requirements-local.txt
docker compose -f docker-compose-image-tag.yml up
superset
meta dbScreenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
18 or greater
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: