You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by ru...@apache.org on 2026/01/21 21:43:48 UTC
(superset) branch fix/databases-redirect created (now 6ef2cfe6ed)
This is an automated email from the ASF dual-hosted git repository.
rusackas pushed a change to branch fix/databases-redirect
in repository https://gitbox.apache.org/repos/asf/superset.git
at 6ef2cfe6ed fix(docs): remove broken /docs/databases redirect to nonexistent path
This branch includes the following new commits:
new 6ef2cfe6ed fix(docs): remove broken /docs/databases redirect to nonexistent path
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
(superset) 01/01: fix(docs): remove broken /docs/databases redirect to nonexistent path
Posted by ru...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
rusackas pushed a commit to branch fix/databases-redirect
in repository https://gitbox.apache.org/repos/asf/superset.git
commit 6ef2cfe6ed602ff4f7b3453fb487daddff5a3cee
Author: Evan Rusackas <ev...@rusackas.com>
AuthorDate: Wed Jan 21 13:43:34 2026 -0800
fix(docs): remove broken /docs/databases redirect to nonexistent path
The .htaccess file had a catch-all redirect that sent all
/docs/databases* URLs to /docs/configuration/databases, which no
longer exists since databases documentation moved to /docs/databases/.
This caused a confusing behavior where clicking a link to
/docs/databases worked (client-side navigation), but refreshing the
page or directly visiting the URL would 301 redirect to a 404.
Changes:
- Remove the catch-all `docs/databases.*` rewrite rule
- Update druid.html redirect to point to /docs/databases
- Update yugabyte redirect to point to /docs/databases
- Fix broken links in quickstart, faq, kubernetes, and timezones docs
Co-Authored-By: Claude Opus 4.5 <no...@anthropic.com>
---
docs/docs/configuration/timezones.mdx | 2 +-
docs/docs/faq.mdx | 4 ++--
docs/docs/installation/kubernetes.mdx | 2 +-
docs/docs/quickstart.mdx | 2 +-
docs/static/.htaccess | 6 ++----
5 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/docs/docs/configuration/timezones.mdx b/docs/docs/configuration/timezones.mdx
index 233e4786fc..a1289d1cb9 100644
--- a/docs/docs/configuration/timezones.mdx
+++ b/docs/docs/configuration/timezones.mdx
@@ -20,7 +20,7 @@ To help make the problem somewhat tractable—given that Apache Superset has no
To strive for data consistency (regardless of the timezone of the client) the Apache Superset backend tries to ensure that any timestamp sent to the client has an explicit (or semi-explicit as in the case with [Epoch time](https://en.wikipedia.org/wiki/Unix_time) which is always in reference to UTC) timezone encoded within.
-The challenge however lies with the slew of [database engines](/docs/configuration/databases#installing-drivers-in-docker-images) which Apache Superset supports and various inconsistencies between their [Python Database API (DB-API)](https://www.python.org/dev/peps/pep-0249/) implementations combined with the fact that we use [Pandas](https://pandas.pydata.org/) to read SQL into a DataFrame prior to serializing to JSON. Regrettably Pandas ignores the DB-API [type_code](https://www.python [...]
+The challenge however lies with the slew of [database engines](/docs/databases#installing-drivers-in-docker) which Apache Superset supports and various inconsistencies between their [Python Database API (DB-API)](https://www.python.org/dev/peps/pep-0249/) implementations combined with the fact that we use [Pandas](https://pandas.pydata.org/) to read SQL into a DataFrame prior to serializing to JSON. Regrettably Pandas ignores the DB-API [type_code](https://www.python.org/dev/peps/pep-024 [...]
For example the following is a comparison of MySQL and Presto,
diff --git a/docs/docs/faq.mdx b/docs/docs/faq.mdx
index d168eacde2..154d668b4e 100644
--- a/docs/docs/faq.mdx
+++ b/docs/docs/faq.mdx
@@ -157,7 +157,7 @@ table afterwards to configure the Columns tab, check the appropriate boxes and s
To clarify, the database backend is an OLTP database used by Superset to store its internal
information like your list of users and dashboard definitions. While Superset supports a
-[variety of databases as data _sources_](/docs/configuration/databases#installing-database-drivers),
+[variety of databases as data _sources_](/docs/databases#installing-database-drivers),
only a few database engines are supported for use as the OLTP backend / metadata store.
Superset is tested using MySQL, PostgreSQL, and SQLite backends. It’s recommended you install
@@ -190,7 +190,7 @@ second etc). Example:
## Does Superset work with [insert database engine here]?
-The [Connecting to Databases section](/docs/configuration/databases) provides the best
+The [Connecting to Databases section](/docs/databases) provides the best
overview for supported databases. Database engines not listed on that page may work too. We rely on
the community to contribute to this knowledge base.
diff --git a/docs/docs/installation/kubernetes.mdx b/docs/docs/installation/kubernetes.mdx
index 06e5991b59..cf8e0542a6 100644
--- a/docs/docs/installation/kubernetes.mdx
+++ b/docs/docs/installation/kubernetes.mdx
@@ -149,7 +149,7 @@ For production clusters it's recommended to build own image with this step done
Superset requires a Python DB-API database driver and a SQLAlchemy
dialect to be installed for each datastore you want to connect to.
-See [Install Database Drivers](/docs/configuration/databases) for more information.
+See [Install Database Drivers](/docs/databases#installing-database-drivers) for more information.
It is recommended that you refer to versions listed in
[pyproject.toml](https://github.com/apache/superset/blob/master/pyproject.toml)
instead of hard-coding them in your bootstrap script, as seen below.
diff --git a/docs/docs/quickstart.mdx b/docs/docs/quickstart.mdx
index 8bc03df368..b92c038fb2 100644
--- a/docs/docs/quickstart.mdx
+++ b/docs/docs/quickstart.mdx
@@ -74,7 +74,7 @@ processes by running Docker Compose `stop` command. By doing so, you can avoid d
From this point on, you can head on to:
- [Create your first Dashboard](/docs/using-superset/creating-your-first-dashboard)
-- [Connect to a Database](/docs/configuration/databases)
+- [Connect to a Database](/docs/databases)
- [Using Docker Compose](/docs/installation/docker-compose)
- [Configure Superset](/docs/configuration/configuring-superset/)
- [Installing on Kubernetes](/docs/installation/kubernetes/)
diff --git a/docs/static/.htaccess b/docs/static/.htaccess
index 4012579253..f056e4423e 100644
--- a/docs/static/.htaccess
+++ b/docs/static/.htaccess
@@ -35,7 +35,7 @@ RewriteRule ^usertutorial\.html$ /docs/using-superset/creating-your-first-dashbo
RewriteRule ^security\.html$ /docs/security/ [R=301,L]
RewriteRule ^sqllab\.html$ /docs/configuration/sql-templating [R=301,L]
RewriteRule ^gallery\.html$ /docs/intro [R=301,L]
-RewriteRule ^druid\.html$ /docs/configuration/databases [R=301,L]
+RewriteRule ^druid\.html$ /docs/databases [R=301,L]
RewriteRule ^misc\.html$ /docs/configuration/country-map-tools [R=301,L]
RewriteRule ^visualization\.html$ /docs/configuration/country-map-tools [R=301,L]
RewriteRule ^videos\.html$ /docs/faq [R=301,L]
@@ -47,7 +47,7 @@ RewriteRule ^docs/installation/email-reports$ /docs/configuration/alerts-reports
RewriteRule ^docs/roadmap$ /docs/intro [R=301,L]
RewriteRule ^docs/contributing/contribution-guidelines$ /docs/contributing/ [R=301,L]
RewriteRule ^docs/contributing/contribution-page$ /docs/contributing/ [R=301,L]
-RewriteRule ^docs/databases/yugabyte/$ /docs/configuration/databases [R=301,L]
+RewriteRule ^docs/databases/yugabyte/$ /docs/databases [R=301,L]
RewriteRule ^docs/frequently-asked-questions$ /docs/faq [R=301,L]
RewriteRule ^docs/installation/running-on-kubernetes/$ /docs/installation/kubernetes [R=301,L]
RewriteRule ^docs/contributing/testing-locally/$ /docs/contributing/howtos [R=301,L]
@@ -62,7 +62,5 @@ RewriteRule ^docs/installation/cache/$ /docs/configuration/cache [R=301,L]
RewriteRule ^docs/installation/async-queries-celery/$ /docs/configuration/async-queries-celery [R=301,L]
RewriteRule ^docs/installation/event-logging/$ /docs/configuration/event-logging [R=301,L]
-RewriteRule ^docs/databases.*$ /docs/configuration/databases [R=301,L]
-
# pre-commit hooks documentation
RewriteRule ^docs/contributing/hooks-and-linting/$ /docs/contributing/development/#git-hooks-1