This is an automated email from the ASF dual-hosted git repository.
rusackas pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/superset.git
The following commit(s) were added to refs/heads/master by this push:
new 36bcdfec97 chore(docs): tidy up supported DB engines for metadata
store (#24080)
36bcdfec97 is described below
commit 36bcdfec97056c7cb5c0eba8d0b25c43209f7d2d
Author: Sam Firke <[email protected]>
AuthorDate: Tue May 16 17:54:37 2023 -0400
chore(docs): tidy up supported DB engines for metadata store (#24080)
---
docs/docs/frequently-asked-questions.mdx | 15 ++++++---------
1 file changed, 6 insertions(+), 9 deletions(-)
diff --git a/docs/docs/frequently-asked-questions.mdx
b/docs/docs/frequently-asked-questions.mdx
index 362ac114f4..381746e650 100644
--- a/docs/docs/frequently-asked-questions.mdx
+++ b/docs/docs/frequently-asked-questions.mdx
@@ -186,17 +186,14 @@ table afterwards to configure the Columns tab, check the
appropriate boxes and s
### What database engine can I use as a backend for Superset?
To clarify, the database backend is an OLTP database used by Superset to store
its internal
-information like your list of users, slices and dashboard definitions.
+information like your list of users and dashboard definitions. While Superset
supports a
+[variety of databases as data
*sources*](https://superset.apache.org/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 for its backend. It’s
recommended you install
-Superset on one of these database server for production.
+Superset is tested using MySQL, PostgreSQL, and SQLite backends. It’s
recommended you install
+Superset on one of these database servers for production. Installation on
other OLTP databases
+may work but isn’t tested. Column-store, non-OLTP databases are not designed
for this type of workload.
-Using a column-store, non-OLTP databases like Vertica, Redshift or Presto as a
database backend
-simply won’t work as these databases are not designed for this type of
workload. Installation on
-Oracle, Microsoft SQL Server, or other OLTP databases may work but isn’t
tested.
-
-Please note that pretty much any databases that have a SqlAlchemy integration
should work perfectly
-fine as a datasource for Superset, just not as the OLTP backend.
### How can I configure OAuth authentication and authorization?
