superset-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [incubator-superset] branch master updated: FAQ entry for backend support (#3282)
Date Tue, 15 Aug 2017 00:57:11 GMT
This is an automated email from the ASF dual-hosted git repository.

maximebeauchemin pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new 6841697  FAQ entry for backend support (#3282)
6841697 is described below

commit 68416979172cfa1126df1954cfa58d99cd23fc39
Author: Maxime Beauchemin <>
AuthorDate: Mon Aug 14 17:57:09 2017 -0700

    FAQ entry for backend support (#3282)
    so that I can close:
 docs/faq.rst | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/faq.rst b/docs/faq.rst
index 12a0198..d06c6c9 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -171,3 +171,16 @@ How do I go about developing a new visualization type?
 Here's an example as a Github PR with comments that describe what the
 different sections of the code do:
+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.
+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.
+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.

To stop receiving notification emails like this one, please contact
['"" <>'].

View raw message