Skip to content

Commit a374f8b

Browse files
Update content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-expiration-example.md
Co-authored-by: andy-stark-redis <164213578+andy-stark-redis@users.noreply.github.com>
1 parent 2f49c22 commit a374f8b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-expiration-example.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ In some cases, you can also set the expiration time based on a field that contai
5555

5656
There are two main approaches you can use to set the expiration time based on a date, datetime, or timestamp field:
5757

58-
- For values representing a passed amount of time e.g. milliseconds since epoch start, you have to convert the value to seconds since epoch and subtracting the current time in seconds since epoch from it.
58+
- For values representing an elapsed time since epoch start (in milliseconds, for example), you have to convert the value to seconds since epoch and then subtract the current time (also in seconds since epoch). The difference between the two is the time until expiration.
5959

6060
```yaml
6161
output:

0 commit comments

Comments
 (0)