tomaszbozek commented on issue #25825:
URL: https://github.com/apache/superset/issues/25825#issuecomment-2037350736
> I have the same problem "Error: no such table" since January. Currently, I
am deploying version `3.1.1` and it's the same behavior: init-db job runs fine,
and if I test the connection to DB is fine. It seems that `init-db` loads all
the examples in the postgresql instance, while the `superset` pod is loading
from a local sqlite (which cannot find, because none created it). So, yes, if I
run `superset load_examples`, the local .db is created and superset can
visualize the examples.
>
> Can you verify that this is how it works? Is it normal to function this
way?
IMHo both pod's should use same volume and same `superset_config.py` and
what is value for `SQLALCHEMY_EXAMPLES_URI` - if its commented out then pod
would use sqllite by default:
`
#
# SQLALCHEMY_EXAMPLES_URI = (
# f"{DATABASE_DIALECT}://"
# f"{EXAMPLES_USER}:{EXAMPLES_PASSWORD}@"
# f"{EXAMPLES_HOST}:{EXAMPLES_PORT}/{EXAMPLES_DB}"
# )
#
`
--
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: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
