You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove references that mention SHA-1 hashes being passed when evaluating server loaded Lua scripts.
The current implementation passes the script itself instead of the hash, generated when the script was initially loaded, due to resiliency concerns.
Copy file name to clipboardexpand all lines: docs/Scripting.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -35,10 +35,10 @@ Any object that exposes field or property members with the same name as @-prefix
35
35
- RedisKey
36
36
- RedisValue
37
37
38
-
StackExchange.Redis handles Lua script caching internally. It automatically transmits the Lua script to redis on the first call to 'ScriptEvaluate'. For further calls of the same script only the hash with [`EVALSHA`](https://redis.io/commands/evalsha) is used.
38
+
StackExchange.Redis handles Lua script caching internally. It automatically transmits the Lua script to redis on the first call to 'ScriptEvaluate'. For further calls of the same script [`EVAL`](https://redis.io/commands/eval) is used instead of [`EVALSHA`](https://redis.io/commands/evalsha), due to resiliency concerns.
39
39
40
40
For more control of the Lua script transmission to redis, `LuaScript` objects can be converted into `LoadedLuaScript`s via `LuaScript.Load(IServer)`.
41
-
`LoadedLuaScripts` are evaluated with the [`EVALSHA`](https://redis.io/commands/evalsha), and referred to by hash.
41
+
`LoadedLuaScripts` are evaluated with the [`EVAL`](https://redis.io/commands/eval) command instead of [`EVALSHA`](https://redis.io/commands/evalsha), due to resiliency concerns.
0 commit comments