Skip to content

Commit 540e878

Browse files
committed
DOC-5412: update KSN page for ROS8.2
1 parent 5084029 commit 540e878

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

content/develop/use/keyspace-notifications.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -83,6 +83,8 @@ following table:
8383
e Evicted events (events generated when a key is evicted for maxmemory)
8484
m Key miss events (events generated when a key that doesn't exist is accessed)
8585
n New key events (Note: not included in the 'A' class)
86+
o Overwritten events (events generated every time a key is overwritten)
87+
c Type-changed events (events generated every time a key's type changes)
8688
A Alias for "g$lshztxed", so that the "AKE" string means all the events except "m" and "n".
8789

8890
At least `K` or `E` should be present in the string, otherwise no event
@@ -150,6 +152,8 @@ Different commands generate different kind of events according to the following
150152
* Every time a key with a time to live associated is removed from the data set because it expired, an `expired` event is generated.
151153
* Every time a key is evicted from the data set in order to free memory as a result of the `maxmemory` policy, an `evicted` event is generated.
152154
* Every time a new key is added to the data set, a `new` event is generated.
155+
* Every time a key is being overwritten, an `overwritten` event is generated.
156+
* Every time a key's type changes, a `type_changed` event is generated.
153157

154158
**IMPORTANT** all the commands generate events only if the target key is really modified. For instance an [`SREM`]({{< relref "/commands/srem" >}}) deleting a non-existing element from a Set will not actually change the value of the key, so no event will be generated.
155159

0 commit comments

Comments
 (0)