You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://codeclimate.com/github/airbnb/superset/coverage)
[](https://gitter.im/airbnb/superset?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[](https://gitter.im/apache/incubator-superset?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
Copy file name to clipboardExpand all lines: docs/faq.rst
+23-4Lines changed: 23 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,8 @@ never be affected by any dashboard level filtering.
107
107
"filter_immune_slice_fields": {
108
108
"177": ["country_name", "__from", "__to"],
109
109
"32": ["__from", "__to"]
110
-
}
110
+
},
111
+
"timed_refresh_immune_slices": [324]
111
112
}
112
113
113
114
In the json blob above, slices 324, 65 and 92 won't be affected by any
@@ -124,15 +125,33 @@ But what happens with filtering when dealing with slices coming from
124
125
different tables or databases? If the column name is shared, the filter will
125
126
be applied, it's as simple as that.
126
127
128
+
129
+
How to limit the timed refresh on a dashboard?
130
+
----------------------------------------------
131
+
By default, the dashboard timed refresh feature allows you to automatically requery every slice on a dashboard according to a set schedule. Sometimes, however, you won't want all of the slices to be refreshed - especially if some data is slow moving, or run heavy queries.
132
+
To exclude specific slices from the timed refresh process, add the ``timed_refresh_immune_slices`` key to the dashboard ``JSON Metadata`` field:
133
+
134
+
..code::
135
+
136
+
{
137
+
"filter_immune_slices": [],
138
+
"expanded_slices": {},
139
+
"filter_immune_slice_fields": {},
140
+
"timed_refresh_immune_slices": [324]
141
+
}
142
+
143
+
In the example above, if a timed refresh is set for the dashboard, then every slice except 324 will be automatically requeried on schedule.
144
+
145
+
127
146
Why does fabmanager or superset freezed/hung/not responding when started (my home directory is NFS mounted)?
superset creates and uses an sqlite database at ``~/.superset/superset.db``. Sqlite is known to `don't work well if used on NFS`__ due to broken file locking implementation on NFS.
148
+
By default, superset creates and uses an sqlite database at ``~/.superset/superset.db``. Sqlite is known to `don't work well if used on NFS`__ due to broken file locking implementation on NFS.
One work around is to create a symlink from ~/.superset to a directory located on a non-NFS partition.
152
+
You can override this path using the ``SUPERSET_HOME`` environment variable.
134
153
135
-
Another work around is to change where superset stores the sqlite database by adding ``SQLALCHEMY_DATABASE_URI = 'sqlite:////new/localtion/superset.db'`` in superset_config.py (create the file if needed), then adding the directory where superset_config.py lives to PYTHONPATH environment variable (e.g. ``export PYTHONPATH=/opt/logs/sandbox/airbnb/``).
154
+
Another work around is to change where superset stores the sqlite database by adding ``SQLALCHEMY_DATABASE_URI = 'sqlite:////new/location/superset.db'`` in superset_config.py (create the file if needed), then adding the directory where superset_config.py lives to PYTHONPATH environment variable (e.g. ``export PYTHONPATH=/opt/logs/sandbox/airbnb/``).
0 commit comments