add new command EXPIRE

[Issif]

For my project, falcosidekick-ui I use redisearch as storage for the events, it works really well but the community asked me to add a TTL to keys. It's not currently possible in this SDK, so updated the Document structure with a new field TTL and created a method SetTTL. I tested my fork in my program, and it works

127.0.0.1:6379> keys *
1) "event:1656512211824943"
2) "event:1656512211824021"
127.0.0.1:6379> TTL event:1656512211824021
(integer) 91
127.0.0.1:6379> TTL event:1656512211824021
(integer) 85

Signed-off-by: Issif issif+github@gadz.org

[chayim]

I can definitely see the value... But perhaps we should at least set a default TTL of -1 during the New.

[Issif]

Without the set, it's by default to -1

[chayim]

Correct - I just prefer being explicit.

[Issif]

I'm in holidays, I'll update this PR when I'm back

[Issif]

I thought and I think we should let the code like this, in this current setup, if the TTL is not set, we follow the Redis default behavior and the keys have no expiration, if we set the TTL, a second command is run to add an expiration to the key. It means, if we don't need to set the TTL we run only 1 command and not 2. For huge workload, it can be useful to avoid to run 2 commands when it's not necessary. wdyt?

[Issif]

Up

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[Issif]

what's the status? thanks

[Issif]

Hi,

My project is using my fork but I would like to plug it on the upstream, what can I do to move forward with this PR please?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud