QT/superset2
1
0
Fork 0
mirror of https://github.com/apache/superset.git synced 2026-07-20 05:36:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: various adjustments across the docs (#29093)

Browse Source 
Co-authored-by: Evan Rusackas <evan@preset.io>
Co-authored-by: John Bodley <4567245+john-bodley@users.noreply.github.com>
This commit is contained in:
Michael Holthausen
2024-06-05 20:53:08 +02:00
committed by GitHub
parent b5d9ac0690
commit de3a1d87b3
8 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/docs/configuration/databases.mdx
View File

@@ -176,7 +176,7 @@ start Python in the Superset application container or host environment and try t
directly to the desired database and fetch data. This eliminates Superset for the
purposes of isolating the problem.
Repeat this process for each different type of database you want Superset to be able to connect to.
Repeat this process for each type of database you want Superset to connect to.
### Database-specific Instructions
@@ -830,7 +830,7 @@ You should then be able to connect to your BigQuery datasets.
To be able to upload CSV or Excel files to BigQuery in Superset, you'll need to also add the
[pandas_gbq](https://github.com/pydata/pandas-gbq) library.
Currently, Google BigQuery python sdk is not compatible with `gevent`, due to some dynamic monkeypatching on python core library by `gevent`.
Currently, the Google BigQuery Python SDK is not compatible with `gevent`, due to some dynamic monkeypatching on python core library by `gevent`.
So, when you deploy Superset with `gunicorn` server, you have to use worker type except `gevent`.