-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Address misleading documentation #2444
base: main
Are you sure you want to change the base?
Address misleading documentation #2444
Conversation
Might be a good idea to update the |
658ef1f
to
cf917c8
Compare
Update: This seems to be irrelevant. |
7e9834a
to
c6893e3
Compare
Thing is... I'm not sure it is wrong. It should still hit the local script cache against our endpoint instance, so once we've seen it load: it should switch to the hash version. I'd want to investigate this via redis-cli monitor before updating any docs (noting that it will still use the full script initially) |
@mgravell Thanks for the heads up, I saw that I'll re-word my changes to make it clear what the current behavior is. |
c6893e3
to
08d7db4
Compare
Add remarks for the evaluation methods of the 'LoadedLuaScript' abstraction which explicitly state that if a SHA-1 hash, of a previously loaded Lua script, was not found in the server cache - it will be reloaded with 'SCRIPT LOAD'. The first evaluation of the reloaded script will be carried out by the 'EVAL' command, but any subsequent evaluations will use 'EVALSHA'.
08d7db4
to
b1d1ac0
Compare
Explicitly mention that if previously loaded 'Lua' script was evaluated by it's 'SHA-1' hash, and that hash doesn't exist on the redis server anymore (e.g. server reboot, SCRIPT FLUSH, etc) - it will be reloaded with the 'SCRIPT LOAD' redis command.
Resolves #2443