All Products
Search

This Product

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

    Document Center

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

    Last Updated:Oct 12, 2025

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

    Note

    Each section in this topic describes the features and compatibility changes provided by the Redis community and Alibaba Cloud. You can also refer to the Tair team and the community's co-authored Redis Major Version Compatibility Report. This report was co-authored 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 Redis 7.0 release notes.

      • For example, for module commands that use background threads, the slow query log records the entire time that a command is suspended. For common block commands such as BLPOP, the slow query log records only the running time, not the suspended time.

    Compatibility

    • For information about the breaking changes for new Redis 7.0 features, see Redis 7.0 release notes.

      • For example, the STRALGO command is replaced with the LCS command.

    • For security reasons, the CONFIG SET, CONFIG GET *, and other related subcommands are disabled. You can query and modify the parameter settings of an instance in the console or by calling OpenAPI operations. For more information, see Configure instance parameters.

    • The allow-oom flag in Lua scripts is no longer supported. For more information, see redis/redis#10699.

    • For information about other changes in supported commands, see Commands supported by Redis Open-Source Edition.

    Redis Open-Source Edition 6.0

    New features

    • For information about the new features of Redis 6.0, see Redis 6.0 release notes.

    • In a cluster instance that uses the direct connection mode, PUBLISH commands are broadcast to all nodes.

    Compatibility

    • For information about the breaking changes for new Redis 6.0 features, see Redis 6.0 release notes.

    • Account management in Tair (Redis OSS-compatible) differs from the Access Control List (ACL) feature in open-source Redis. The following describes the account management mechanism in Tair (Redis OSS-compatible):

      • Two accounts are available for an instance: the default account named default and an account that is named after the instance, such as r-bp1857n194kiuv****.

      • If you do not specify an account when you use the AUTH command to connect to a Redis instance, the default account is used for authentication.

      • If the account that you specify does not exist when you use the AUTH command to connect to a Redis instance, the -WRONGPASS invalid username-password pair error is returned. The system does not automatically switch to the default account for authentication.

      • After you enable password-free access for an instance in a VPC, if you use the AUTH command to connect and the specified account does not exist or you specify an incorrect password, the system returns the -WRONGPASS invalid username-password pair error. The system no longer returns OK.

    • When you use the CONFIG GET command, you must specify a configuration item. Wildcard characters (*) are not supported.

    • For information about other changes in supported commands, see Commands supported by Redis Open-Source Edition.

    Redis Open-Source Edition 5.0

    New features

    Compatibility

    • For information about the breaking changes for new Redis 5.0 features, see Redis 5.0 release notes.

      • For example, the results of commands that are executed in Lua scripts are no longer sorted.

    • Account names are case-sensitive.

    • After you enable password-free access for an instance in a VPC, you can use the AUTH command to switch between different accounts for password-free connections.

      Note

      If you grant different permissions to different accounts, ensure that your application runs commands within the scope of the granted permissions. Otherwise, an error indicating insufficient permissions is returned.

    • The READONLY and READWRITE commands are available.

    • There are differences between cloud-native instances and classic instances. After you enable password-free access for a cloud-native instance, all connections to the instance must be authenticated using a whitelist, and the #no_loose_check-whitelist-always parameter cannot be set.

    • For information about other changes in supported commands, see Commands supported by Redis Open-Source Edition.

    Redis Open-Source Edition 4.0 (retired)

    Expand to view details

    New features

    • For information about the new features of Redis 4.0, see Redis 4.0 release notes.

    • The audit log feature is supported.

    • The real-time hot key statistics feature is supported.

    • After you enable password-free access for an instance in a VPC, you can set the #no_loose_check-whitelist-always parameter to specify whether to authenticate connections from the same VPC against a whitelist. For more information, see Supported parameters.

    • The Sentinel-compatible mode is supported. You must enable VPC password-free access to use this mode. Only the SENTINEL and get-master-addr-by-name subcommands are supported.

    • You can create multiple accounts and grant read/write or read-only permissions to the accounts. Account names are not case-sensitive. You can use the AUTH user:password command to switch between accounts.

      • The default account is named after the instance, such as r-bp1857n194kiuv****.

      • If you do not specify an account or the specified account does not exist, the system automatically uses the default account for authentication.

      • If you enable password-free access, no authentication is required for connections. The default account is used and you cannot switch to a different account.

    • You can enable the direct connection mode for cluster instances.

    • For cluster instances, you can set the ptod_enabled parameter to pass through client IP addresses to DB nodes. For more information, see Supported parameters.

    Compatibility

    • For information about the breaking changes for new Redis 4.0 features, see Redis 4.0 release notes.

      • For example, in the cluster architecture, slot-to-key mappings must be recorded. This results in higher memory usage for the same amount of data compared with the standard architecture.

      • For example, in the cluster architecture, the SORT command does not support the BY and GET parameters.

    • Secure Sockets Layer (SSL) encryption is no longer supported.

    • Cluster instances in direct connection mode do not support some CLUSTER commands. For more information, see Commands supported by Redis Open-Source Edition.

    • Cluster instances in direct connection mode support the SELECT command.

      Note

      You can no longer use the SELECT command to determine whether the current connection is in cluster mode. Otherwise, a false positive may occur.

    • In a cluster instance that uses the direct connection mode, PUBLISH commands are not broadcast to other nodes.

    • For information about other changes in supported commands, see Commands supported by Redis Open-Source Edition.

    Redis Open-Source Edition 2.8 (retired)

    Expand to view details

    New features

    Compatibility

    • For information about the breaking changes for new Redis 2.8 features, see Redis 2.8 release notes.

    • Some debugging and management commands are not supported. For more information, see Commands supported by Redis Open-Source Edition.

    • Limited support is provided for the CONFIG SET/GET commands:

      • CONFIG GET: This command returns only some configuration items. Security-related configuration items are not returned.

      • CONFIG SET: This command returns OK but does not modify parameters.

    • Limited support is provided for the INFO command. For example, security-related information, such as Persistence and Replication, is not returned.

    • Cluster instances in proxy mode do not support some commands. For more information, see Command limitations for cluster and read/write splitting instances.