Hi, I'm uncertain whether you're trying to upgrade an existing deployment or installing a new deployment, but Superset needs it's own database (which is specified in the SQLAlchemy URI). If you're creating a new deployment you should follow these <https://superset.apache.org/installation.html#superset-installation-and-initialization> instructions, which creates the necessary database tables and populate them with the Flask App Builder (FAB) security permissions as well as the example dataset. If you're simply upgrading to a newer version you should follow these <https://superset.apache.org/installation.html#upgrading> instructions.
-John On Tue, May 15, 2018 at 10:48 AM, arindos.ext...@gmail.com < arindos.ext...@gmail.com> wrote: > I am attempting to deploy superset 0.24.0 with my MySQL server set in the > ‘SQLALCHEMY_DATABASE_URI’ field. The issue I run into is superset attempts > to create a ‘logs’ table on my database, on which I already have a table > named logs so a create conflict occurs and superset fails to start. What > other tables are setup by default by Superset? Can I change the name of > them in a startup config? Is there an easy way around this problem I face? >
