General purpose redis client
ExponentialRetry
backoff policy (#1921 by @gliljas)DefaultOptionsProvider
support for endpoint-based defaults configuration (#1987 by @NickCraver)SUBSCRIBE
is disabled, give proper errors and connect faster (#2001 by @NickCraver)GET
on SET
command support (present in Redis 6.2+ - #2003 by @martinekvili)CLUSTER
command is disabled (#2014 by @tylerohlsen)ConfigurationOptions.BacklogPolicy
is available - old behavior is configured via options.BacklogPolicy = BacklogPolicy.FailFast
. This backlogs nothing and fails commands immediately if no connection is available.StreamEntry
constructor public for better unit test experience (#1923 by @WeihanLi)EVAL
instead EVALSHA
(#1930 by @martinpotter)CLIENT LIST
can more easily see what's connected (#1985 by @NickCraver)LPOP
, RPOP
, SRANDMEMBER
, and SPOP
(#1993 by @NickCraver)NodeMaintenanceScaleComplete
event (handles Redis cluster scaling) (#1902 by @NickCraver)Condition
APIs (transactions), now supports StreamLengthEqual
and variants (#1807 by @AlphaGremlin)ListLeftPop
, ListLeftPopAsync
, ListRightPop
, and ListRightPopAsync
(#1850 by @jjfmarket)StringGetDelete
/StringGetDeleteAsync
APIs for Redis GETDEL
command(#1840 by @WeihanLi)GetOutstandingCount
could obscure underlying faults by faulting itself (#1792 by @mgravell)ReconfigureAsync
re-entrancy (caused connection issues) ([1772 by @NickCraver)ReconfigureAsync
Sentinel race resulting in NoConnectionAvailable when using DemandMaster (#1773 by @NickCraver)RPUSHX
/LPUSHX
methods (#1620 by @stefanloerwald)CheckCertificateRevocation
can be controlled via the config string (#1591 by @lwlwalker)ROLE
support (#1551 by @zmj)RPUSHX
/LPUSHX
support (#1557 by @dmytrohridin)Int64
parse scenario (#1568 by @arsnyder16)[*]SCAN
- fix possible NRE scenario if the iterator is disposed with an incomplete operation in flight (by @mgravell)[*]SCAN
- treat the cursor as an opaque value whenever possible, for compatibility with redis-cluster-proxy
(by @mgravell)[*]SCAN
- include additional exception data in the case of faults (by @mgravell)System.IO.Pipelines
to 4.7.1, and identifies new System.Buffers
binding failure on 4.7.2 (by @mgravell)