Cannot Get Redis Key Value
See original GitHub issueHi -
Not sure what I am doing wrong but I cannot seem to get the Redis key value.
If I do something like:
await redis.set('key', 'value',)
const data = await redis.get('key')
console.log(data)
I get back a hashed string like dmFsdWU=
. How do I resolve this to the actual value (‘value’). I am using @upstash/redis in Nextjs api routes.
Issue Analytics
- State:
- Created 9 months ago
- Comments:8
Top Results From Across the Web
Can not get key value from Redis in Express js - Stack Overflow
I have a node express application running on localhost:3500 on windows 10 . I am using redis for storing refresh tokens .
Read more >How to Get All Keys in Redis | Tutorial by Chartio
Most (But Not All) Objects Use a Key For the vast majority of data storage with Redis, data will be stored in a...
Read more >client.get return undefined even tho key value exists #1783
client. get return undefined even tho key value exists · Issue #1783 · redis/node-redis · GitHub.
Read more >Redis - A Key/Value Store - UVA Research Computing
As a dictionary, Redis allows you to set and retrieve pairs of keys and values. Think of a “key” as a unique identifier...
Read more >Redis - npm
A modern, high performance Redis client. Latest version: 4.5.1, last published: a month ago. Start using redis in your project by running ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please try creating your redis instance like this:
I’m investigating this problem right now
can you tell me your redis version and runtime? also when did this start happening?
Yes I just figured this out as well. thank you so much for reporting it.
I’ll be working on a fix for nodejs14 but in the meantime you need to either use
responseEncoding: false
or upgrade to at least node v16 @btahir @anishsrinivasan