the feature 'Querying across databases' doesn't work

[actuo]

following the documentation to enable meta database and can't find database of type "Superset meta database" in add new database window. the feature flag (ENABLE_SUPERSET_META_DB )mentioned in documentation can not be found in https://github.com/apache/superset/blob/master/RESOURCES/FEATURE_FLAGS.md.

How to reproduce the bug

set the ENABLE_SUPERSET_META_DB feature flag to true
add a new database of type "Superset meta database" with the SQLAlchemy URI "superset://".

Expected results

the database of type "Superset meta database" shows at available database list in add database windows
what you expected to happen.

Actual results

No such type of database shows

Screenshots

Environment

(please complete the following information):

• browser type and version: chrome Version 117.0.5938.132
• superset version: 3.0.0
• python version: 3.9.6
• node.js version: v16.20.2
• any feature flags active:ENABLE_SUPERSET_META_DB= True ,WTF_CSRF_ENABLED = True

Checklist

Make sure to follow these steps before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

[ozbillwang]

Someone mentioned in Slack that it will be released in version 3.1.0, but we are uncertain about the release date.

https://apache-superset.slack.com/archives/C016B3LG5B4/p1696459438961999

[PierrickVoulet]

I confirm I can see the Superset Meta DB type in 3.1.0 version

[nevotheless]

I'm using 3.1.0 as well, and tried setting ENABLE_SUPERSET_META_DB to True inside the superset_config.py, saved the secret restarted my deployment, pods getting recreated but i don't see it.

There's also no mention of that feature on the supported feature flag documentation page and know i don't really know where to set the feature flag instead.

[rusackas]

Just opened a PR to add the feature flag to the relevant page:
#27071
@betodealmeida feel free to categorize that if you'd like :)

The feature is indeed in 3.1 (see changelog here) so that's not what @nevotheless is up against.

I'm closing this issue because the issue as-reported (not being in 3.0.0) isn't relevant. Questions about its existence in 3.1 have been addressed. Getting into the intricacies of why a particular deployment isn't updating should be filed as a new/separate issue, or taken to the #deploying-superset channel on Superset Slack

[GauravJain98]

@nevotheless i found this issue and fixed this bug later this might help you
https://superset.apache.org/docs/installation/running-on-kubernetes/#superset_configpy