blob: 3f507a8af2a01ee284f47b1f649c7cb5791f7a8e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
Removes the specified entries from a stream, and returns the number of entries
deleted, that may be different from the number of IDs passed to the command in
case certain IDs do not exist.
Normally you may think at a Redis stream as an append-only data structure,
however Redis streams are represented in memory, so we are able to also delete
entries. This may be useful, for instance, in order to comply with certain
privacy policies.
# Understanding the low level details of entries deletion
Redis streams are represented in a way that makes them memory efficient: a radix
tree is used in order to index macro-nodes that pack linearly tens of stream
entries. Normally what happens when you delete an entry from a stream is that
the entry is not _really_ evicted, it just gets marked as deleted.
Eventually if all the entries in a macro-node are marked as deleted, the whole
node is destroyed and the memory reclaimed. This means that if you delete a
large amount of entries from a stream, for instance more than 50% of the entries
appended to the stream, the memory usage per entry may increment, since what
happens is that the stream will start to be fragmented. However the stream
performances will remain the same.
In future versions of Redis it is possible that we'll trigger a node garbage
collection in case a given macro-node reaches a given amount of deleted entries.
Currently with the usage we anticipate for this data structure, it is not a good
idea to add such complexity.
@return
@integer-reply: the number of entries actually deleted.
@examples
```
> XADD mystream * a 1
1538561698944-0
> XADD mystream * b 2
1538561700640-0
> XADD mystream * c 3
1538561701744-0
> XDEL mystream 1538561700640-0
(integer) 1
127.0.0.1:6379> XRANGE mystream - +
1) 1) 1538561698944-0
2) 1) "a"
2) "1"
2) 1) 1538561701744-0
2) 1) "c"
2) "3"
```
|
