ApsaraDB for Redis:Commands supported by ApsaraDB for Redis Community Edition

ApsaraDB for Redis is compatible with multiple open source Redis versions.

• DRAM-based instances of the Enhanced Edition (Tair) that are compatible with 6.0: Redis 6.2 and earlier. In addition, these instances support extended data modules of Tair.

• DRAM-based instances of the Enhanced Edition (Tair) that are compatible with 5.0: Redis 5.0 and earlier. In addition, these instances support extended data modules of Tair.

• Persistent memory-optimized instances of the Enhanced Edition (Tair): Redis 6.0 and earlier. These instances have limits on specific commands. For more information, see Limits on commands supported by ApsaraDB for Redis Enhanced Edition (Tair).

• ESSD-based instances of the Enhanced Edition (Tair): Redis 4.0 and earlier. These instances have limits on specific commands. For more information, see Limits on commands supported by ApsaraDB for Redis Enhanced Edition (Tair).

• Hybrid-storage instances (phased out) of the Enhanced Edition (Tair): Redis 4.0 and earlier.

• Community Edition instances: All major versions such as Redis 7.0, 6.0, 5.0 and 4.0. These instances provide backward compatibility.

The following list describes the symbols that are used in the tables of this topic.

• ✔️ indicates that this command is supported.

• ❌ indicates that this command is not supported.

• ➖ indicates that the command is not supported in open source Redis. For example, the TOUCH command is supported only by Redis 3.2.1 and later. This command is marked as ➖ in the Redis 2.8 column of the table.

• Footnote ①: If you want to run the command on a cluster instance, you must enable the direct connection mode to use a private endpoint to connect to the instance. For more information, see Use a private endpoint to connect to a Tair instance. You can also run the command if you use the endpoint of a proxy node to connect to an instance.

• Footnote ②: The CONFIG SET command returns only OK. The command does not modify the parameters. This ensures that the instance remains compatible with specific client frameworks.

• In this topic, instances of the latest minor version are used. Part of the commands is supported only for instances of versions later than a specific version. For more information, see Release notes for minor versions of ApsaraDB for Redis Community Edition and ApsaraDB for Redis proxy nodes.