Making use of jedis get set expire mget #6

New Issue

2020-12-03T12:49:05Z

ham1255 commented

2020-12-03 12:49:05 +00:00

(Migrated from github.com)

No description provided.

GovindasOM commented

2020-12-04 15:16:24 +00:00

(Migrated from github.com)

what is this?

ham1255 commented

2020-12-10 08:09:52 +00:00

(Migrated from github.com)

Since jedis has same stuff like skript variables so we could store string data
In redis since we can hash::uuid > some data
And expire isnfor when stored data key get removed in seconds and delete deletes ofc

Since jedis has same stuff like skript variables so we could store string data In redis since we can hash::uuid > some data And expire isnfor when stored data key get removed in seconds and delete deletes ofc

ham1255 commented

2020-12-27 04:00:59 +00:00

(Migrated from github.com)

Currently thinking of

Get new jedis instance and store it in {jedis1}

Get string from redis using {jedis1} and the key is "hi" and store results on {results}

Broadcast "%{results}%"

Close jedis instance {jedis1} //not closing the jedis will cause pool being exhausted + memory leak so close it after you use it

Currently thinking of Get new jedis instance and store it in {jedis1} Get string from redis using {jedis1} and the key is "hi" and store results on {results} Broadcast "%{results}%" Close jedis instance {jedis1} //not closing the jedis will cause pool being exhausted + memory leak so close it after you use it

GovindasOM commented

2021-09-19 08:43:08 +00:00

(Migrated from github.com)

I am closing this issue due to inactivity and no real need for it that I can see right now

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Limework/RediSkript#6