Tair (Enterprise Edition) provides instances of multiple engine versions and architectures. Tair instances of different engine versions and architectures support different Redis commands. This topic describes the native Redis commands supported by Tair (Enterprise Edition) and the limits on these commands.
Commands supported by Tair (Enterprise Edition)
Tair (Enterprise Edition) instance series are compatible with multiple open source Redis versions.
Tair DRAM-based instances that are compatible with Redis 7.0: Redis 7.0 and earlier. In addition, this instance series supports the extended data structures of Tair.
Tair DRAM-based instances that are compatible with Redis 6.0: Redis 6.2 and earlier. In addition, this instance series supports the extended data structures of Tair.
Tair DRAM-based instances that are compatible with Redis 5.0: Redis 5.0 and earlier. In addition, this instance series supports the extended data structures of Tair.
Tair persistent memory-optimized instances: Redis 6.0 and earlier. This instance series has limits on specific commands. For more information, see Limits on commands supported by Tair.
Tair ESSD/SSD-based instances: Redis 6.0 and earlier. This instance series has limits on specific commands. For more information, see Limits on commands supported by Tair.
The following list describes the symbols that are used in the following tables:
✔️️️️ indicates that this command is supported.
❌ indicates that this command is not supported.
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 the direct connection mode to connect to a cluster 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. If your business requires modifications to parameters, you can use the console or call API operations to modify the parameters. For more information, see Configure instance parameters.This topic focuses on the availability of commands for instances of the latest minor version. Some commands are supported only for instances of versions later than a specific version. For more information, see Release notes for Tair minor versions and Release notes for minor versions of proxy nodes.
By default, commands in all command groups are supported by standard instances, cluster instances, and read/write splitting instances. Cluster instances and read/write splitting instances have limits on specific commands. For more information, see Limits on commands supported by cluster instances and read/write splitting instances.
Additional limits on the commands supported by Tair (Redis OSS-compatible) persistent memory-optimized and ESSD/SSD-based instances
The following section describes the limits on commands supported by the latest minor version of Tair (Enterprise Edition). If your instance has more limits, update the minor version of the instance and try again. For more information, see Update the minor version of an instance.
For information about the release notes, see Release notes for Tair minor versions.
For information about how to configure parameters, see Configure instance parameters.
Persistent memory-optimized instances
Command group
Limits
Keys
The MOVE and RENAME commands must be enabled by using the pena_rename_move_compatible_enabled parameter.
Server management
The SWAPDB command is not supported.
ESSD/SSD-based instances
Command group
Unsupported command
Hyperloglog
The PFADD, PFCOUNT, or PFMERG command is not supported.
Keys
The MOVE, OBJECT, SORT, or TOUCH command is not supported.
The Rename and RenameNX commands have a maximum limit on the size of the keys they can modify, which is governed by the max-rename-commit-size parameter. By default, this limit is set to 16 MB.
Server management
The SWAPDB command is not supported.
The FLUSHDB command can be run synchronously, but not asynchronously. Exercise caution when you run the FLUSHDB command in a production environment.
Streams
Commands for working with streams are not supported.
Scripting
Lua scripting commands, such as EVAL, EVALSHA, and SCRIPT EXISTS, can be enabled and disabled by using the txn-isolation-lock and #no_loose_lua-strict-mode parameters.
Transactions
Transaction-related commands, such as DISCARD, EXEC, and WATCH, can be enabled and disabled by using the txn-isolation-lock parameter.