Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mGet() and mSet() function to redis adaptor #731

Open
mtuchi opened this issue Aug 21, 2024 · 0 comments
Open

Add mGet() and mSet() function to redis adaptor #731

mtuchi opened this issue Aug 21, 2024 · 0 comments

Comments

@mtuchi
Copy link
Collaborator

mtuchi commented Aug 21, 2024

Background

The redis adaptor supports basic Redis commands, it lacks support for the mGet() and mSet() commands, which are essential for efficiently handling multiple key-value pairs in Redis.

Feature Request

I propose adding two new helper methods to the Redis adaptor: mGet() and mSet(). These methods should mirror the functionality of Redis's native json.mGet and json.mSet commands, allowing us to retrieve and set multiple key-value pairs in a single operation.

Implementation Details

  1. mGet(keys: Array<string>):

    • Accepts an array of strings, where each string is a key in Redis.
    • Returns an array of values corresponding to the provided keys.
  2. mSet(keyValuePairs: Object):

    • Accepts an object where each key-value pair corresponds to a Redis key and its associated value.
    • Sets all the key-value pairs in Redis in a single operation.

Use Cases

  • mGet(): This will be particularly useful when retrieving multiple related values from Redis in a single call, reducing the need for multiple jGet operations and improving performance.
  • mSet(): This will allow us to efficiently store multiple key-value pairs at once, which is beneficial when working with bulk data.

Redis Docs

@github-project-automation github-project-automation bot moved this to New Issues in v2 Aug 21, 2024
@christad92 christad92 moved this from New Issues to Backlog in v2 Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants