Do you mean the database configuration entries in the Superset database? Those are stored in the metadata database, and the config key SQLALCHEMY_DATABASE_URI defines where that lives. Either your configuration changed, or the database changed.
Note that by default Superset uses a sqlite database in a temp folder, which won't work if you have multiple boxes or won't be persisted if you spin up a new box. Max On Wed, Aug 15, 2018 at 7:52 AM Vinay Kumar Sharma <[email protected]> wrote: > Dear Team, > > We have created Amazon Cloud instance on their EC2 service and configured > the application *Apache Superset*. After installation, we have configured > few databased on it and all were going well i.e.: database connections, > tables, slices, dashboard etc. All of sudden (after 28 days) the populated > contents and databases are not available. The strange thing is the > application is available but databases which we have created those have > been gone. In this context, we are writing you what could be the possible > reason behind this issue? > > We request you to please inform us so that prior to move our > infrastructure, we understand the limitations. > > Thanks & Regards > Vinay >
