New features and compatibility of major versions of Redis Open-Source Edition - Tair (Redis® OSS-Compatible)

You can create instances that run different versions of Redis Open-Source Edition in Tair (Redis OSS-compatible). This topic describes the new features and compatibility changes for each major version of Redis Open-Source Edition.

Note

Each section describes the feature and compatibility changes from the community and Alibaba Cloud. You can also refer to the Redis Major Version Compatibility Report, which was co-developed by the Tair team and the community.

Redis Open-Source Edition 7.0

New features

For information about the new features of Redis 7.0, see the 7.0 release note.
- For example, for module commands that use background threads, the slow query log feature records the entire suspension time. In contrast, for regular blocking commands such as BLPOP, the slow query log feature records only the running time and not the suspension time.

Compatibility

For information about breaking changes from the community, see the 7.0 release note.
- For example, the STRALGO command is no longer supported and is replaced by the LCS command.
For security purposes, the CONFIG SET, CONFIG GET *, and other subcommands are disabled. You can query and modify instance parameters in the console or using OpenAPI. For more information, see Set parameters.
The allow-oom flag in Lua scripts is no longer supported. For more information, see redis/redis#10699.
For information about other command support changes, see Command support for Redis Open-Source Edition.

Redis Open-Source Edition 6.0

New features

For information about the new features of Redis 6.0, see the 6.0 release note.
In the direct connection mode for a cluster architecture, the PUBLISH command is broadcast across the cluster.

Compatibility

For information about breaking changes from the community, see the 6.0 release note.
Account management differs from the community Access Control List (ACL) account permissions. The following section describes account management in Tair (Redis OSS-compatible):
- The default account is default. The account named after the instance, such as r-bp1857n194kiuv****, is a separate account.
- When you connect to Redis using the AUTH command, the default account is used for authentication if no account is specified.
For information about other command support changes, see Command support for Redis Open-Source Edition.

Redis Open-Source Edition 5.0

New features

For information about the new features of Redis 5.0, see the 5.0 release note.
Support for latency insight is available.
Support for real-time statistics on large keys is available.
Support for Transport Layer Security (TLS) encryption is available.
The wake-up time precision for blocking connections is optimized.
The direct connection mode for a cluster architecture supports seamless scaling.

Compatibility

For information about breaking changes from the community, see the 5.0 release note.
- For example, commands executed by Lua scripts no longer sort the results.
Account names are case-sensitive.
After passwordless access over a VPC is enabled, you can use the AUTH command to switch between different accounts for passwordless connections.
Note
If your accounts have different permissions, make sure that your application executes commands only within the scope of the permissions. Otherwise, a permission error is reported.
The READONLY and READWRITE commands are available.
The cloud-native edition and the classic edition have some differences. For a cloud-native edition instance, after passwordless access over a VPC is enabled, all connections still require whitelist authentication, and you cannot set the #no_loose_check-whitelist-always parameter.
For information about other command support changes, see Command support for Redis Open-Source Edition.

Redis Open-Source Edition 4.0 (Discontinued)

Click to view details

New features

For information about the new features of Redis 4.0, see the 4.0 release note.
Support for audit logs is available.
Support for real-time statistics on hot keys is available.
After passwordless access over a VPC is enabled, you can set the #no_loose_check-whitelist-always parameter to specify whether to perform whitelist authentication for network connections from the same VPC. For more information, see Parameter support.
Support for Sentinel-compatible mode is available. This feature requires you to enable passwordless access over a VPC. Only the SENTINEL and get-master-addr-by-name subcommands are supported.
You can create multiple accounts. Account names are case-insensitive. You can set read/write or read-only permissions for the accounts. You can also use the AUTH user:password command to switch between accounts.
- The default account is named after the instance, such as r-bp1857n194kiuv****.
- If no account is specified or the specified account does not exist, the system automatically uses the default account (named after the instance) for authentication.
- If passwordless access over a VPC is enabled, passwordless connections do not require authentication. The default account is used, and you cannot switch accounts.
The cluster architecture supports enabling a direct connection mode address.
The cluster architecture lets you set the ptod_enabled parameter to pass through client IP addresses to DB nodes. For more information, see Parameter support.

Compatibility

For information about breaking changes from the community, see the 4.0 release note.
- For example, in a cluster architecture, the slot-to-key mapping must be recorded. Therefore, the same amount of data consumes more memory than in a standard architecture.
- For example, in a cluster architecture, the SORT command does not support the BY and GET parameters.
Secure Sockets Layer (SSL) encryption is no longer supported.
The direct connection mode for a cluster architecture does not support some CLUSTER commands. For more information, see Command support for Redis Open-Source Edition.
The direct connection mode for a cluster architecture supports the SELECT command.
Note
You can no longer use the SELECT command to determine whether the current connection is in cluster mode. If you do, misjudgments may occur.
In the direct connection mode for a cluster architecture, the PUBLISH command is not broadcast to other nodes.
For information about other command support changes, see Command support for Redis Open-Source Edition.

Redis Open-Source Edition 2.8 (Discontinued)

Click to view details

New features

For information about the new features of Redis 2.8, see the 2.8 release note.
Support for setting whitelists is available.
Support for passwordless access over a VPC is available. After this feature is enabled:
- Network connections from within the VPC do not require IP whitelist authentication.
- When a network connection from within the VPC executes the AUTH command, OK is returned without password authentication.
Support for Secure Sockets Layer (SSL) encryption is available.
Support for disabling commands is available.
The cluster architecture supports the proxy mode.

Compatibility

For information about breaking changes from the community, see the 2.8 release note.
Some debugging and management commands are not supported. For more information, see Command support for Redis Open-Source Edition.
Limited support for the CONFIG SET/GET commands is provided:
- CONFIG GET: Returns only some configuration items. Security-related configuration items are not returned.
- CONFIG SET: Returns only OK and does not modify the parameters.
Limited support for the INFO command is provided. For example, security-related information such as Persistence and Replication is not returned.
The proxy mode for a cluster architecture does not support some commands. For more information, see Command limits for cluster and read/write splitting instances.