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

chore: various markdown warnings resolved (#30657)

Browse Source 
Co-authored-by: Evan Rusackas <evan@preset.io>
This commit is contained in:
Emad Rad
2025-03-04 23:15:49 +03:30
committed by GitHub
parent 807dcddc28
commit 2b53b1800e
20 changed files with 158 additions and 159 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/docs/faq.mdx
View File

@@ -66,7 +66,7 @@ For running long query from Sql Lab, by default Superset allows it run as long a
being killed by celery. If you want to increase the time for running query, you can specify the
timeout in configuration. For example:
```
```python
SQLLAB_ASYNC_TIME_LIMIT_SEC = 60 * 60 * 6
```
@@ -78,7 +78,7 @@ come back within client-side timeout (60 seconds by default), Superset will disp
to avoid gateway timeout message. If you have a longer gateway timeout limit, you can change the
timeout settings in **superset_config.py**:
```
```python
SUPERSET_WEBSERVER_TIMEOUT = 60
```
@@ -87,7 +87,7 @@ SUPERSET_WEBSERVER_TIMEOUT = 60
You need to register a free account at [Mapbox.com](https://www.mapbox.com), obtain an API key, and add it
to **.env** at the key MAPBOX_API_KEY:
```
```python
MAPBOX_API_KEY = "longstringofalphanumer1c"
```
@@ -99,7 +99,7 @@ refreshed - especially if some data is slow moving, or run heavy queries. To exc
from the timed refresh process, add the `timed_refresh_immune_slices` key to the dashboard JSON
Metadata field:
```
```json
{
"filter_immune_slices": [],
"expanded_slices": {},
@@ -115,7 +115,7 @@ Slice refresh will also be staggered over the specified period. You can turn off
setting the `stagger_refresh` to false and modify the stagger period by setting `stagger_time` to a
value in milliseconds in the JSON Metadata field:
```
```json
{
"stagger_refresh": false,
"stagger_time": 2500
@@ -137,7 +137,7 @@ You can override this path using the **SUPERSET_HOME** environment variable.
Another workaround is to change where superset stores the sqlite database by adding the following in
`superset_config.py`:
```
```python
SQLALCHEMY_DATABASE_URI = 'sqlite:////new/location/superset.db?check_same_thread=false'
```
@@ -157,12 +157,12 @@ 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/configuration/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
Superset on one of these database servers for production. Installation on other OLTP databases
may work but isn’t tested. It has been reported that [Microsoft SQL Server does *not*
may work but isn’t tested. It has been reported that [Microsoft SQL Server does _not_
work as a Superset backend](https://github.com/apache/superset/issues/18961). Column-store,
non-OLTP databases are not designed for this type of workload.
@@ -236,7 +236,7 @@ made to cover more and more use cases.
The API available is documented using [Swagger](https://swagger.io/) and the documentation can be
made available under **/swagger/v1** by enabling the following flag in `superset_config.py`:
```
```python
FAB_API_SWAGGER_UI = True
```