-
Notifications
You must be signed in to change notification settings - Fork 2
/
properties.yaml
57 lines (57 loc) · 1.94 KB
/
properties.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
version: 0.1.0
spec:
units: []
properties:
- property: &credentialsSecret
propertyNames:
- name: "credentialsSecret"
kind:
type: "env"
datatype:
type: "string"
roles:
- name: "node"
required: true
asOfVersion: "0.0.0"
description: "The secret where the Superset credentials are stored."
- property: &rowLimit
propertyNames:
- name: "ROW_LIMIT"
kind:
type: "file"
file: "superset_config.py"
datatype:
type: "integer"
defaultValues:
- fromVersion: "0.0.0"
value: "50000"
recommendedValues:
- fromVersion: "0.0.0"
value: "50000"
roles:
- name: "node"
required: false
asOfVersion: "0.0.0"
description: "Row limit when requesting chart data. Corresponds to ROW_LIMIT"
- property: &webserverTimeout
propertyNames:
- name: "SUPERSET_WEBSERVER_TIMEOUT"
kind:
type: "file"
file: "superset_config.py"
datatype:
type: "integer"
defaultValues:
- fromVersion: "0.0.0"
value: "60" # 1 min
recommendedValues:
# The default timeout of Superset is 60s which is way to low when querying "big data" systems.
# Especially Trino queries often take longer.
# see [the Superset docs](https://superset.apache.org/docs/frequently-asked-questions#why-are-my-queries-timing-out).
- fromVersion: "0.0.0"
value: "300" # 5 min
roles:
- name: "node"
required: true
asOfVersion: "0.0.0"
description: "Maximum number of seconds a Superset request can take before timing out. This settings effect the maximum duration a query to an underlying datasource can take. If you get timeout errors before your query returns the result you can need to increase this timeout. Corresponds to SUPERSET_WEBSERVER_TIMEOUT"