All Products
Search
Document Center

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

Last Updated:Jan 16, 2026

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

Note

Each section describes the features and compatibility changes from the open-source community and Alibaba Cloud. For more information, see 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 records the entire suspension time. In contrast, for regular blocking commands such as BLPOP, the slow query log records only the running time, not the suspension time.

Compatibility

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.

  • The Account Management feature is different from open-source Redis ACL permissions. The following describes the Account Management feature for 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

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 you enable passwordless access over a VPC, you can still use the AUTH command to switch between accounts.

    Note

    If your accounts have different permissions, make sure that your application executes commands that are within the scope of the account's permissions. Otherwise, a permission error occurs.

  • The READONLY and READWRITE commands are available.

  • The cloud-native and classic editions have a key difference. On a cloud-native edition instance, after you enable passwordless access over a VPC, 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.

  • Adds support for audit logs.

  • Adds support for real-time statistics on hot keys.

  • After you enable passwordless access over a VPC, you can set the #no_loose_check-whitelist-always parameter to control whether to perform whitelist authentication for connections from within the same VPC. For more information, see Parameter support.

  • Adds support for Sentinel-compatible mode. This feature requires passwordless access over a VPC to be enabled. Only the SENTINEL and get-master-addr-by-name subcommands are supported.

  • You can create multiple accounts with case-insensitive names. You can set read/write or read-only permissions for each account and use the AUTH user:password command to switch between them.

    • 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 you enable passwordless access for a VPC, connections will not require authentication and will use the default account. You cannot switch accounts.

  • The cluster architecture lets you enable 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, slot-to-key mappings must be recorded. This causes the same amount of data to consume more memory than it would 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. Using the command for this purpose may lead to incorrect assessments.

  • 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

Compatibility

  • For information about breaking changes from the community, see the 2.8 release notes.

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

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

    • CONFIG GET: Returns only some configuration items. Security-related configuration items are not returned.

    • CONFIG SET: Returns an OK response but does not modify any parameters.

  • The INFO command has limited support. For example, security-related information, such as the Persistence and Replication sections, is not returned.

  • Some commands are not supported in proxy mode for instances that use a cluster architecture. For more information, see Command limits for cluster and read/write splitting instances.