Skip to content

DOC-4316 fixed broken CSC links #723

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

Merged
merged 1 commit into from
Oct 1, 2024
Merged

DOC-4316 fixed broken CSC links #723

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion content/commands/client-caching/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ title: CLIENT CACHING
This command controls the tracking of the keys in the next command executed
by the connection, when tracking is enabled in `OPTIN` or `OPTOUT` mode.
Please check the
[client side caching documentation]({{< relref "/develop/use/client-side-caching" >}}) for
[client side caching documentation]({{< relref "/develop/connect/clients/client-side-caching" >}}) for
background information.

When tracking is enabled Redis, using the [`CLIENT TRACKING`]({{< relref "/commands/client-tracking" >}}) command, it is
Expand Down
2 changes: 1 addition & 1 deletion content/commands/client-getredir/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ syntax_str: ''
title: CLIENT GETREDIR
---
This command returns the client ID we are redirecting our
[tracking]({{< relref "/develop/use/client-side-caching" >}}) notifications to. We set a client
[tracking]({{< relref "/develop/connect/clients/client-side-caching#tracking" >}}) notifications to. We set a client
to redirect to when using [`CLIENT TRACKING`]({{< relref "/commands/client-tracking" >}}) to enable tracking. However in
order to avoid forcing client libraries implementations to remember the
ID notifications are redirected to, this command exists in order to improve
Expand Down
4 changes: 2 additions & 2 deletions content/commands/client-tracking/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ syntax_str: "[REDIRECT\_client-id] [PREFIX\_prefix [PREFIX prefix ...]] [BCAST]
title: CLIENT TRACKING
---
This command enables the tracking feature of the Redis server, that is used
for [server assisted client side caching]({{< relref "/develop/use/client-side-caching" >}}).
for [server assisted client side caching]({{< relref "/develop/connect/clients/client-side-caching#tracking" >}}).

When tracking is enabled Redis remembers the keys that the connection
requested, in order to send later invalidation messages when such keys are
Expand All @@ -85,7 +85,7 @@ when the RESP3 protocol is used) or redirected in a different connection
available where clients participating in this protocol receive every
notification just subscribing to given key prefixes, regardless of the
keys that they requested. Given the complexity of the argument please
refer to [the main client side caching documentation]({{< relref "/develop/use/client-side-caching" >}}) for the details. This manual page is only a reference for the options of this subcommand.
refer to [the main client side caching documentation]({{< relref "/develop/reference/client-side-caching" >}}) for the details. This manual page is only a reference for the options of this subcommand.

In order to enable tracking, use:

Expand Down
2 changes: 1 addition & 1 deletion content/commands/client-trackinginfo/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ syntax_fmt: CLIENT TRACKINGINFO
syntax_str: ''
title: CLIENT TRACKINGINFO
---
The command returns information about the current client connection's use of the [server assisted client side caching]({{< relref "/develop/use/client-side-caching" >}}) feature.
The command returns information about the current client connection's use of the [server assisted client side caching]({{< relref "/develop/connect/clients/client-side-caching" >}}) feature.

Here's the list of tracking information sections and their respective values:

Expand Down
2 changes: 1 addition & 1 deletion content/develop/connect/clients/client-side-caching.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ client-side caching works well in the very common use case where a small subset
is accessed much more frequently than the rest of the data (according
to the [Pareto principle](https://en.wikipedia.org/wiki/Pareto_principle)).

## Updating the cache when the data changes
## Updating the cache when the data changes {#tracking}

All caching systems must implement a scheme to update data in the cache
when the corresponding data changes in the main database. Redis uses an
Expand Down
2 changes: 1 addition & 1 deletion content/develop/data-types/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ weight: 35
---

Redis is a data structure server.
At its core, Redis provides a collection of native data types that help you solve a wide variety of problems, from [caching]({{< relref "/develop/use/client-side-caching" >}}) to
At its core, Redis provides a collection of native data types that help you solve a wide variety of problems, from [caching]({{< relref "/develop/data-types/strings" >}}) to
[queuing]({{< relref "/develop/data-types/lists" >}}) to
[event processing]({{< relref "/develop/data-types/streams" >}}).
Below is a short description of each data type, with links to broader overviews and command references.
Expand Down
Loading