CLIENT CACHING documented.

Author: antirez

commands.json

@@ -361,6 +361,22 @@
     "since": "5.0.0",
     "group": "sorted_set"
   },
+  "CLIENT CACHING": {
+    "summary": "Instruct the server about tracking or not keys in the next request",
+    "complexity": "O(1)",
+    "arguments": [
+      {
+        "name": "mode",
+        "type": "enum",
+        "enum": [
+          "YES",
+          "NO"
+        ]
+      }
+    ],
+    "since": "6.0.0",
+    "group": "server"
+  },
   "CLIENT ID": {
     "summary": "Returns the client ID for the current connection",
     "complexity": "O(1)",

commands/client-caching.md

@@ -0,0 +1,22 @@
+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](/topics/client-side-caching) for
+background informations.
+
+When tracking is enabled Redis, using the `CLIENT TRACKING` command, it is
+possible to specify the `OPTIN` or `OPTOUT` options, so that keys
+in read only commands are not automatically remembered by the server to
+be invalidated later. When we are in `OPTIN` mode, we can enable the
+tracking of the keys in the next command by calling `CLIENT CACHING yes`
+immediately before it. Similarly when we are in `OPTOUT` mode, and keys
+are normally tracked, we can avoid the keys in the next command to be
+tracked using `CLIENT CACHING no`.
+
+Basically the command sets a state in the connection, that is valid only
+for the next command execution, that will modify the behavior of client
+tracking.
+
+@return
+
+@simple-string-reply: `OK` or an error if the argument is not yes or no.