redis/README.md

291 lines
9.5 KiB
Markdown
Raw Permalink Normal View History

# Redis client for Go
2017-06-17 13:01:40 +03:00
2023-01-23 09:48:54 +03:00
[![build workflow](https://github.com/redis/go-redis/actions/workflows/build.yml/badge.svg)](https://github.com/redis/go-redis/actions)
[![PkgGoDev](https://pkg.go.dev/badge/github.com/redis/go-redis/v9)](https://pkg.go.dev/github.com/redis/go-redis/v9?tab=doc)
2020-09-18 09:24:22 +03:00
[![Documentation](https://img.shields.io/badge/redis-documentation-informational)](https://redis.uptrace.dev/)
[![codecov](https://codecov.io/github/redis/go-redis/graph/badge.svg?token=tsrCZKuSSw)](https://codecov.io/github/redis/go-redis)
2022-03-18 15:00:38 +03:00
[![Chat](https://discordapp.com/api/guilds/752070105847955518/widget.png)](https://discord.gg/rWtp5Aj)
2020-09-02 09:41:39 +03:00
2022-04-03 09:27:24 +03:00
> go-redis is brought to you by :star: [**uptrace/uptrace**](https://github.com/uptrace/uptrace).
2022-09-15 12:01:14 +03:00
> Uptrace is an open-source APM tool that supports distributed tracing, metrics, and logs. You can
> use it to monitor applications and set up automatic alerts to receive notifications via email,
2022-11-09 16:18:55 +03:00
> Slack, Telegram, and others.
>
2023-10-20 08:41:48 +03:00
> See [OpenTelemetry](https://github.com/redis/go-redis/tree/master/example/otel) example which
> demonstrates how you can use Uptrace to monitor go-redis.
2022-05-03 17:50:48 +03:00
## How do I Redis?
[Learn for free at Redis University](https://university.redis.com/)
[Build faster with the Redis Launchpad](https://launchpad.redis.com/)
[Try the Redis Cloud](https://redis.com/try-free/)
[Dive in developer tutorials](https://developer.redis.com/)
[Join the Redis community](https://redis.com/community/)
[Work at Redis](https://redis.com/company/careers/jobs/)
2023-02-11 12:32:44 +03:00
## Documentation
- [English](https://redis.uptrace.dev)
- [简体中文](https://redis.uptrace.dev/zh/)
2022-02-22 16:18:47 +03:00
## Resources
2023-01-23 09:48:54 +03:00
- [Discussions](https://github.com/redis/go-redis/discussions)
2022-03-19 15:32:12 +03:00
- [Chat](https://discord.gg/rWtp5Aj)
2023-01-23 09:48:54 +03:00
- [Reference](https://pkg.go.dev/github.com/redis/go-redis/v9)
- [Examples](https://pkg.go.dev/github.com/redis/go-redis/v9#pkg-examples)
2020-06-10 15:04:12 +03:00
2020-06-09 17:59:23 +03:00
## Ecosystem
2023-01-24 15:19:26 +03:00
- [Redis Mock](https://github.com/go-redis/redismock)
2022-02-22 16:18:47 +03:00
- [Distributed Locks](https://github.com/bsm/redislock)
- [Redis Cache](https://github.com/go-redis/cache)
2023-01-24 16:50:10 +03:00
- [Rate limiting](https://github.com/go-redis/redis_rate)
2020-06-09 17:59:23 +03:00
2022-09-15 12:01:14 +03:00
This client also works with [Kvrocks](https://github.com/apache/incubator-kvrocks), a distributed
key value NoSQL database that uses RocksDB as storage engine and is compatible with Redis protocol.
2022-04-14 17:55:34 +03:00
2020-06-09 17:59:23 +03:00
## Features
2014-05-11 11:42:40 +04:00
- Redis commands except QUIT and SYNC.
- Automatic connection pooling.
2022-04-13 16:01:35 +03:00
- [Pub/Sub](https://redis.uptrace.dev/guide/go-redis-pubsub.html).
- [Pipelines and transactions](https://redis.uptrace.dev/guide/go-redis-pipelines.html).
- [Scripting](https://redis.uptrace.dev/guide/lua-scripting.html).
- [Redis Sentinel](https://redis.uptrace.dev/guide/go-redis-sentinel.html).
- [Redis Cluster](https://redis.uptrace.dev/guide/go-redis-cluster.html).
- [Redis Ring](https://redis.uptrace.dev/guide/ring.html).
- [Redis Performance Monitoring](https://redis.uptrace.dev/guide/redis-performance-monitoring.html).
2023-08-15 10:19:19 +03:00
- [Redis Probabilistic [RedisStack]](https://redis.io/docs/data-types/probabilistic/)
2014-05-11 11:42:40 +04:00
2015-10-25 14:30:26 +03:00
## Installation
2014-05-11 11:42:40 +04:00
2020-10-12 17:02:00 +03:00
go-redis supports 2 last Go versions and requires a Go version with
[modules](https://github.com/golang/go/wiki/Modules) support. So make sure to initialize a Go
module:
2014-05-11 11:42:40 +04:00
2020-05-09 17:38:45 +03:00
```shell
2019-12-09 10:54:23 +03:00
go mod init github.com/my/repo
2016-10-12 15:11:09 +03:00
```
2023-01-23 09:48:54 +03:00
Then install go-redis/**v9**:
2016-10-12 15:11:09 +03:00
2020-10-12 17:02:00 +03:00
```shell
2023-01-23 09:48:54 +03:00
go get github.com/redis/go-redis/v9
2016-10-12 15:11:09 +03:00
```
2015-10-25 14:30:26 +03:00
## Quickstart
2015-05-23 14:33:33 +03:00
2020-05-09 17:38:45 +03:00
```go
2020-06-14 13:45:37 +03:00
import (
"context"
"fmt"
"github.com/redis/go-redis/v9"
2020-06-14 13:45:37 +03:00
)
var ctx = context.Background()
2015-05-23 14:33:33 +03:00
func ExampleClient() {
2020-06-10 15:04:12 +03:00
rdb := redis.NewClient(&redis.Options{
2020-05-26 12:07:28 +03:00
Addr: "localhost:6379",
Password: "", // no password set
DB: 0, // use default DB
})
2020-10-12 17:02:00 +03:00
2020-06-10 15:04:12 +03:00
err := rdb.Set(ctx, "key", "value", 0).Err()
2020-05-26 12:07:28 +03:00
if err != nil {
panic(err)
}
2020-06-10 15:04:12 +03:00
val, err := rdb.Get(ctx, "key").Result()
2020-05-26 12:07:28 +03:00
if err != nil {
panic(err)
}
fmt.Println("key", val)
2020-06-10 15:04:12 +03:00
val2, err := rdb.Get(ctx, "key2").Result()
2020-05-26 12:07:28 +03:00
if err == redis.Nil {
fmt.Println("key2 does not exist")
} else if err != nil {
panic(err)
} else {
fmt.Println("key2", val2)
}
// Output: key value
// key2 does not exist
2015-05-23 14:33:33 +03:00
}
```
2023-10-20 08:39:54 +03:00
The above can be modified to specify the version of the RESP protocol by adding the `protocol`
option to the `Options` struct:
```go
rdb := redis.NewClient(&redis.Options{
Addr: "localhost:6379",
Password: "", // no password set
DB: 0, // use default DB
Protocol: 3, // specify 2 for RESP 2 or 3 for RESP 3
})
```
### Connecting via a redis url
2023-10-20 08:39:54 +03:00
go-redis also supports connecting via the
[redis uri specification](https://github.com/redis/redis-specifications/tree/master/uri/redis.txt).
The example below demonstrates how the connection can easily be configured using a string, adhering
to this specification.
```go
import (
"github.com/redis/go-redis/v9"
)
func ExampleClient() *redis.Client {
url := "redis://user:password@localhost:6379/0?protocol=3"
opts, err := redis.ParseURL(url)
if err != nil {
panic(err)
}
return redis.NewClient(opts)
}
```
### Advanced Configuration
go-redis supports extending the client identification phase to allow projects to send their own custom client identification.
#### Default Client Identification
By default, go-redis automatically sends the client library name and version during the connection process. This feature is available in redis-server as of version 7.2. As a result, the command is "fire and forget", meaning it should fail silently, in the case that the redis server does not support this feature.
#### Disabling Identity Verification
When connection identity verification is not required or needs to be explicitly disabled, a `DisableIndentity` configuration option exists. In V10 of this library, `DisableIndentity` will become `DisableIdentity` in order to fix the associated typo.
To disable verification, set the `DisableIndentity` option to `true` in the Redis client options:
```go
rdb := redis.NewClient(&redis.Options{
Addr: "localhost:6379",
Password: "",
DB: 0,
DisableIndentity: true, // Disable set-info on connect
})
```
#### Unstable RESP3 Structures for RediSearch Commands
When integrating Redis with application functionalities using RESP3, it's important to note that some response structures aren't final yet. This is especially true for more complex structures like search and query results. We recommend using RESP2 when using the search and query capabilities, but we plan to stabilize the RESP3-based API-s in the coming versions. You can find more guidance in the upcoming release notes.
To enable unstable RESP3, set the option in your client configuration:
```go
redis.NewClient(&redis.Options{
UnstableResp3: true,
})
```
**Note:** When UnstableResp3 mode is enabled, it's necessary to use RawResult() and RawVal() to retrieve a raw data.
Since, raw response is the only option for unstable search commands Val() and Result() calls wouldn't have any affect on them:
```go
res1, err := client.FTSearchWithArgs(ctx, "txt", "foo bar", &redis.FTSearchOptions{}).RawResult()
val1 := client.FTSearchWithArgs(ctx, "txt", "foo bar", &redis.FTSearchOptions{}).RawVal()
```
2023-09-20 10:42:45 +03:00
## Contributing
Please see [out contributing guidelines](CONTRIBUTING.md) to help us improve this library!
2015-10-25 14:30:26 +03:00
## Look and feel
2014-05-11 11:42:40 +04:00
Some corner cases:
2020-05-09 17:38:45 +03:00
```go
2018-07-20 11:47:53 +03:00
// SET key value EX 10 NX
2020-06-10 15:04:12 +03:00
set, err := rdb.SetNX(ctx, "key", "value", 10*time.Second).Result()
2015-05-23 14:33:33 +03:00
// SET key value keepttl NX
set, err := rdb.SetNX(ctx, "key", "value", redis.KeepTTL).Result()
2018-07-20 11:47:53 +03:00
// SORT list LIMIT 0 2 ASC
2020-06-10 15:04:12 +03:00
vals, err := rdb.Sort(ctx, "list", &redis.Sort{Offset: 0, Count: 2, Order: "ASC"}).Result()
2014-05-11 11:42:40 +04:00
2018-07-20 11:47:53 +03:00
// ZRANGEBYSCORE zset -inf +inf WITHSCORES LIMIT 0 2
2020-06-10 15:04:12 +03:00
vals, err := rdb.ZRangeByScoreWithScores(ctx, "zset", &redis.ZRangeBy{
2020-05-26 12:07:28 +03:00
Min: "-inf",
Max: "+inf",
Offset: 0,
Count: 2,
2018-07-20 11:47:53 +03:00
}).Result()
2014-05-11 11:42:40 +04:00
2018-07-20 11:47:53 +03:00
// ZINTERSTORE out 2 zset1 zset2 WEIGHTS 2 3 AGGREGATE SUM
2020-06-10 15:04:12 +03:00
vals, err := rdb.ZInterStore(ctx, "out", &redis.ZStore{
2020-05-26 12:07:28 +03:00
Keys: []string{"zset1", "zset2"},
Weights: []int64{2, 3}
2020-04-12 12:27:32 +03:00
}).Result()
2014-05-11 11:42:40 +04:00
2018-07-20 11:47:53 +03:00
// EVAL "return {KEYS[1],ARGV[1]}" 1 "key" "hello"
2020-06-10 15:04:12 +03:00
vals, err := rdb.Eval(ctx, "return {KEYS[1],ARGV[1]}", []string{"key"}, "hello").Result()
2016-03-19 17:55:22 +03:00
2019-06-04 13:32:54 +03:00
// custom command
2020-06-10 15:04:12 +03:00
res, err := rdb.Do(ctx, "set", "key", "value").Result()
2016-03-10 12:10:47 +03:00
```
2021-02-25 18:58:15 +03:00
## Run the test
2021-02-25 18:58:15 +03:00
go-redis will start a redis-server and run the test cases.
2021-04-29 08:45:13 +03:00
The paths of redis-server bin file and redis config file are defined in `main_test.go`:
2021-02-25 18:58:15 +03:00
2022-04-13 16:01:35 +03:00
```go
var (
redisServerBin, _ = filepath.Abs(filepath.Join("testdata", "redis", "src", "redis-server"))
redisServerConf, _ = filepath.Abs(filepath.Join("testdata", "redis", "redis.conf"))
)
```
2021-02-25 18:58:15 +03:00
For local testing, you can change the variables to refer to your local files, or create a soft link
to the corresponding folder for redis-server and copy the config file to `testdata/redis/`:
2022-04-13 16:01:35 +03:00
```shell
ln -s /usr/bin/redis-server ./go-redis/testdata/redis/src
cp ./go-redis/testdata/redis.conf ./go-redis/testdata/redis/
```
Lastly, run:
2021-02-25 18:58:15 +03:00
2022-04-13 16:01:35 +03:00
```shell
go test
```
2021-07-14 14:40:25 +03:00
2023-10-20 08:39:54 +03:00
Another option is to run your specific tests with an already running redis. The example below, tests
against a redis running on port 9999.:
```shell
REDIS_PORT=9999 go test <your options>
```
2022-04-05 10:06:50 +03:00
## See also
- [Golang ORM](https://bun.uptrace.dev) for PostgreSQL, MySQL, MSSQL, and SQLite
- [Golang PostgreSQL](https://bun.uptrace.dev/postgres/)
- [Golang HTTP router](https://bunrouter.uptrace.dev/)
- [Golang ClickHouse ORM](https://github.com/uptrace/go-clickhouse)
2021-07-14 14:40:25 +03:00
## Contributors
Thanks to all the people who already contributed!
2023-01-23 09:48:54 +03:00
<a href="https://github.com/redis/go-redis/graphs/contributors">
<img src="https://contributors-img.web.app/image?repo=redis/go-redis" />
2021-07-14 14:40:25 +03:00
</a>