All Products
Search

This Product

    Tair (Redis® OSS-Compatible):Major version features and compatibility

    Document Center

    Tair (Redis® OSS-Compatible):Major version features and compatibility

    Last Updated:Mar 30, 2026

    Tair (Redis OSS-compatible) supports multiple engine versions. This page covers the new features and compatibility changes for each major version — including both open-source community changes and Alibaba Cloud-specific behavior.

    Each section covers features and compatibility changes from the open-source community and Alibaba Cloud. For a community-maintained view, see the Redis Major Version Compatibility Report, a joint effort by the Tair team and the community.

    Tair (Enterprise Edition)

    New features

    • Extended data structures: Versions 5.0 and later include Tair extended data structures, which provide richer data models and enterprise-grade capabilities. For details, see Overview of Tair extended data structures.

    Compatibility changes

    There are no compatibility changes between versions 6.0 and 7.0. The table below covers behavioral differences introduced when upgrading from version 5.0 to 6.0. For per-version command support, see Command support and limitations for Tair (Enterprise Edition).

    Extended data structure Change (5.0 → 6.0) Impact
    TairHash (exHash) When using the pattern parameter with EXHSCAN: version 5.0 runs expiration checks only on fields matching the pattern; version 6.0 runs expiration checks on all scanned fields, regardless of match. Scanning with a large count value when many fields have expired may increase response time (RT) in version 6.0.
    TairBloom (Bloom) The underlying hash algorithm is updated. The false positive rate may increase slightly.
    TairTS (TS) EXTS.S.ALTER: Invalid attributes such as CHUNK_SIZE are silently ignored in version 6.0; they trigger an error in version 5.0. EXTS.S.INFO: The maxDataPoints field is no longer returned in version 6.0. EXTS.S.RANGE / EXTS.P.RANGE: The unsupported withLabels parameter is silently ignored in version 6.0; it triggers an error in version 5.0. Queries: Query buckets can be smaller than 1 second in version 6.0, which was not allowed in version 5.0. Check whether your application relies on the error-triggering behavior of EXTS.S.ALTER or EXTS.S.RANGE / EXTS.P.RANGE. Update any client code that reads the maxDataPoints field from EXTS.S.INFO responses.

    Redis open-source edition 7.0

    New features

    See the Redis 7.0 release notes for the full list of new features.

    One notable behavior change: for module commands that run on background threads, the slow log records the entire pending time. For standard blocking commands such as BLPOP, the slow log records only the execution time, not the pending time.

    Compatibility changes

    See the Redis 7.0 release notes for all breaking changes. Key changes to be aware of:

    • The LCS command replaces STRALGO. STRALGO is no longer supported.

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

    For other command support changes, see Redis Open-Source Edition command support.

    Redis open-source edition 6.0

    New features

    See the Redis 6.0 release notes for the full list of new features.

    One Alibaba Cloud-specific addition: in a cluster architecture instance using direct connection mode, the PUBLISH command now broadcasts across the entire cluster.

    Compatibility changes

    See the Redis 6.0 release notes for all breaking changes.

    Account management in Tair (Redis OSS-compatible) differs from the open-source Access Control List (ACL) feature:

    • The default account is default. The account named after the instance ID (for example, r-bp1857n194kiuv****) is a separate, distinct account.

    • Running AUTH without specifying an account authenticates against the default account.

    For other command support changes, see Redis Open-Source Edition command support.

    Redis open-source edition 5.0

    New features

    See the Redis 5.0 release notes for the full list of new features.

    Alibaba Cloud-specific additions in this version:

    Compatibility changes

    See the Redis 5.0 release notes for all breaking changes. Key changes to be aware of:

    • Commands executed in Lua scripts no longer sort results.

    • Account names are case-sensitive.

    • After enabling password-free access, the AUTH command can still switch between accounts.

    • The READONLY and READWRITE commands are available.

    Account permissions: If different accounts have different permissions, make sure your application only executes commands within the permitted scope — otherwise it will encounter permission errors.

    Cloud-native Edition vs. Classic Edition: After enabling virtual private cloud (VPC) password-free access for a Cloud-native Edition instance, all connections still require allowlist verification. The #no_loose_check-whitelist-always parameter is not available for Cloud-native Edition instances.

    For other command support changes, see Redis Open-Source Edition command support.

    Retired versions

    The following versions are retired. Information is provided for reference when migrating away from these versions.

    Redis open-source edition 4.0

    New features

    See the Redis 4.0 release notes for the full list of new features.

    Alibaba Cloud-specific additions in this version:

    • Audit logs

    • Real-time hotkey statistics

    • Sentinel-compatible mode: requires password-free access and supports only the SENTINEL and get-master-addr-by-name subcommands.

    • Direct connection mode address for cluster architecture instances.

    • The ptod_enabled parameter, which passes client IP addresses to database nodes. See Supported parameters.

    • Multiple accounts with read/write or read-only permissions. Switch accounts with the AUTH user:password command.

      • Account names are case-insensitive in version 4.0.

      • The default account is the instance ID (for example, r-bp1857n194kiuv****).

      • If an account is not specified or does not exist, authentication falls back to the default account.

      • When password-free access is enabled, connections use the default account and cannot switch accounts.

    • The #no_loose_check-whitelist-always parameter for password-free access, which controls whether allowlist verification applies to same-VPC connections. See Supported parameters.

    Compatibility changes

    See the Redis 4.0 release notes for all breaking changes. Key changes to be aware of:

    • Cluster architecture instances must record slot-to-key mappings, resulting in higher memory usage for the same dataset compared to standard architecture.

    • In cluster architecture, the SORT command does not support the BY and GET parameters.

    • SSL encryption is no longer supported.

    • In direct connection mode for cluster architecture instances, some CLUSTER commands are not supported. See Redis Open-Source Edition command support.

    • In direct connection mode for cluster architecture instances, the SELECT command is supported — but do not use it to detect whether a connection is in cluster mode, as this can cause your application to misidentify the connection type.

    • In direct connection mode for cluster architecture instances, the PUBLISH command does not broadcast to other nodes.

    For other command support changes, see Redis Open-Source Edition command support.

    Redis open-source edition 2.8

    New features

    See the Redis 2.8 release notes for the full list of new features.

    Alibaba Cloud-specific additions in this version:

    Compatibility changes

    See the Redis 2.8 release notes for all breaking changes. Key changes to be aware of:

    • Some debugging and management commands are not supported.

    • CONFIG GET returns only a subset of configuration items. Security-related configuration items are not returned.

    • CONFIG SET always returns OK without applying any changes.

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

    • Cluster architecture instances in proxy mode do not support some commands. See Command limitations for cluster and read/write splitting instances.