-
Notifications
You must be signed in to change notification settings - Fork 531
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
Return of DEL operation in redis #523
Comments
Odd. I'm unable to duplicate using redis-cli and the local redis port (6379) vs dynamite port (8102). Both return 1 on del key. I'm using the dev branch as of the Dec 18 commit. How about you? |
FWIW, I'm seeing these lines in log output:
v0.6.5 |
The command should be |
Oops, so this might be operator error, after all. 😄 I managed to find red:delete Lua calls, where it probably should have been red:del then. Thanks for the answer, @shailesh33 I'll investigate further what's really goin' on there. |
Yeah, it was an error on our part. Thanks once again @shailesh33 and sorry for the noise! |
This issue has been answered. |
Hello guys, I don't know if this is a problem with dynomite implementation or with the redis python package.
When I delete a key from redis it returns 1 and when I delete a key in dynomite it returns Null. So when using redis python package with the dynomite it throws a TypeError exception because it is expecting the return to be 1 instead of Null.
The text was updated successfully, but these errors were encountered: