From f8fcdee0a78ba5fcb13523c0d3e15c51056e0274 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Julius=20R=C3=BCberg?= Date: Wed, 15 Jul 2026 21:24:33 +0200 Subject: [PATCH] Fix description of Unix socket-based Redis connection OpenDAL parses the URI with http::Uri which _expects_ a host. If no host is specified parsing is going to fail. --- docs/Redis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Redis.md b/docs/Redis.md index 33e9283a7..103169fdb 100644 --- a/docs/Redis.md +++ b/docs/Redis.md @@ -6,7 +6,7 @@ If you want to use a Redis cluster, set `SCCACHE_REDIS_CLUSTER_ENDPOINTS` instea Redis endpoint URL format can be found in the [OpenDAL source code](https://github.com/apache/opendal/blob/5f1d5d1d61ed28f63d4955538b33a4d582feebef/core/src/services/redis/backend.rs#L268-L307). Some valid examples: * `redis://127.0.0.1:6379` or `tcp://127.0.0.1:6379` or `127.0.0.1:6379` - TCP-based Redis connection (non-secure) * `rediss://@1.2.3.4:6379` - TLS-based Redis connection over TCP (secure) -* `unix:///tmp/redis.sock` or `redis+unix:///tmp/redis.sock` - Unix socket-based Redis connection +* `unix://localhost/tmp/redis.sock` or `redis+unix://localhost/tmp/redis.sock` - Unix socket-based Redis connection Redis can be configured as a LRU (least recently used) cache with a fixed maximum cache size. Set `maxmemory` and `maxmemory-policy` according to the [Redis documentation](https://redis.io/topics/lru-cache). The `allkeys-lru` policy which discards the *least recently accessed or modified* key fits well for the sccache use case.