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
|`jobs`|[`/v1/pre-aggregations/jobs`][ref-ref-paj]| ❌ No |
@@ -248,9 +248,20 @@ should be unique for each separate request. `spanId` should define user
248
248
interaction span such us `Continue wait` retry cycle and it's value shouldn't
249
249
change during one single interaction.
250
250
251
-
## Troubleshooting
251
+
## Cache control
252
252
253
-
### `Continue wait`
253
+
[`/v1/load`][ref-ref-load] and [`/v1/cubesql`][ref-ref-cubesql] endpoints of the REST API
254
+
allow to control the cache behavior. The following querying strategies with regards to
255
+
the cache are supported:
256
+
257
+
| Strategy | Description |
258
+
| --- | --- |
259
+
|`stale-if-slow`| If [refresh keys][ref-refresh-keys] are up-to-date, returns cached value. If expired, tries to return fresh value from the data source. If the data source query is slow (hits [`Continue wait`](#continue-wait)), returns stale value from cache. |
260
+
|`stale-while-revalidate`| If [refresh keys][ref-refresh-keys] are up-to-date, returns cached value. If expired, returns stale data from cache and updates cache in background. |
261
+
|`must-revalidate`| If [refresh keys][ref-refresh-keys] are up-to-date, returns cached value. If expired, always waits for fresh value from the data source, even if slow (hits one or more [`Continue wait`](#continue-wait) intervals). |
262
+
|`no-cache`| Skips [refresh key][ref-refresh-keys] checks. Always returns fresh data from the data source, regardless of cache or query performance. |
263
+
264
+
## `Continue wait`
254
265
255
266
If the request takes too long to be processed, the REST API responds with
256
267
`{ "error": "Continue wait" }` and the status code 200.
0 commit comments