Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add entity cache note #6083

Merged
merged 3 commits into from
Oct 3, 2024
Merged

docs: add entity cache note #6083

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5739854
Add configuration note
Meschreiber Sep 30, 2024
937518a
Merge branch 'main' into docs/entity-cache-config-note
Meschreiber Oct 2, 2024
7a8bcbd
Update docs/source/configuration/entity-caching.mdx
Meschreiber Oct 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/source/configuration/entity-caching.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,15 @@ preview_entity_cache:
private_id: "user_id"
```


<Note>

In router v1.51 and earlier, Redis and per-subgraph caching configurations are set directly on `preview_entity_cache`, for example `preview_entity_cache.redis`.

This configuration may change while the feature is in [preview](/resources/product-launch-stages/#product-launch-stages).

</Note>

### Configure time to live (TTL)

Besides configuring a global TTL for all the entries in Redis, the GraphOS Router also honors the [`Cache-Control` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control) returned with the subgraph response. It generates a `Cache-Control` header for the client response by aggregating the TTL information from all response parts.
Expand Down