Help Center/ GeminiDB/ GeminiDB Redis API/ Development Reference/ Compatible Commands
Updated on 2025-07-29 GMT+08:00
View PDF
Share

Compatible Commands

GeminiDB Redis API provides cluster and primary/standby instances. It is compatible with Redis Community Edition 5.0 and earlier versions, Redis 6.2 (including 6.2.X), and Redis 7.0 commands. You do not need to modify code when migrating applications to the cloud.

This section describes the compatibility of commands supported by GeminiDB Redis API 5.0, 6.2 (including 6.2.X), and 7.0, providing references to DBAs and developers.

Basic GeminiDB Commands

The following table lists commands provided by community Redis and compatibility of GeminiDB Redis API 5.0, 6.2 (including 6.2.X), and 7.0.

Table 1 Command compatibility of GeminiDB Redis API

Redis Command Classification

Description

Compatibility with GeminiDB Redis 5.0

Compatibility with GeminiDB Redis API 6.2 (Including 6.2.x)

Compatibility with GeminiDB Redis API 7.0

String

String commands

100%

100%

100%

Hash

Hash commands

100%

100%

100%

List

List commands

100%

100%

100%

Sorted set

Sorted set commands

100%

100%

100%

Set

Set commands

100%

100%

100%

Bitmap

Bitmap commands

100%

100%

100%

Stream

Stream commands

100%

The XGROUP subcommand createconsumer is not supported.

Features of version 7.0 are not supported.

GEO

GEO commands

100%

100%

100%

HyperLogLog

HyperLogLog commands

100%

100%

100%

Pub/Sub

Pub/Sub commands

100%

100%

100%

Lua scripts

Lua commands

100%

100%

Features of version 7.0 are not supported.

Transactions

Transaction commands

100%

100%

100%

Generic

Generic key commands

SWAPDB and MOVE commands are not supported.

The following commands are not supported:

SWAPDB and MOVE

100%

GeminiDB Redis API is compatible with some CLUSTER commands, including CLUSTER INFO, CLUSTER KEYSLOT, CLUSTER MYID, CLUSTER NODES, CLUSTER SLOTS, CLUSTER SHARDS and CLUSTER HELP.

Advanced GeminiDB Commands

  • ExHash
    • Application scenarios: GeminiDB allows you to set an expiration time for each field of a hash key and is suitable for services such as frequency control and shopping cart.
    • Command list: See ExHash Commands.
    • Usage: See ExHash for Ad Frequency Control.
  • Bloom filter
    • Functions: A Bloom filter enables you to check if an element is present in a large-size collection. It is applicable to scenarios such as web interceptors and anti-cache penetration.
    • Command list: See Bloom filter.
    • Usage: See Bloom filter description.

GeminiDB O&M Commands

GeminiDB provides comprehensive and easy-to-use O&M functions based on the community Redis commands such as INFO, CLIENT, SLOWLOG, MONITOR, and CONFIG.

Table 2 O&M functions of GeminiDB Redis API

Function

Description

Redis Community Edition Command/Capability

Metrics

QPS, average latency, and p99 latency of commands, various metrics of nodes, and aggregation metrics of instances are provided.

INFO

Instance sessions

Client IP addresses and the top sessions of an instance are displayed. Users can kill sessions in batches with a few clicks.

CLIENT

Parameter configuration

Kernel parameters can be queried and modified with only a few clicks. Enhancement of CONFIG command provided by Redis Community Edition.

CONFIG

Viewing slow query logs

Slow query logs and diagnosis information can be displayed.

SLOWLOG

User permission management

The account management function is supported.

ACL (Access Control List)

Viewing audit logs

High-risk commands and operations can be audited.

MONITOR

Real-time big key diagnosis

Big keys are monitored in real time and without affecting services.

Not supported

Real-time hot key diagnosis

Hot keys are monitored in real time and without affecting services.

Not supported

Real-time key prefix analysis

Distribution of key prefixes is monitored in real time, which does not affect services.

Not supported

Critical command renaming

Users can modify command aliases and view renaming records.

You can rename commands by modifying configuration files.

Abnormal key circuit break

Specified keys can be shielded in one click to avoid access to services, which can be used for rapid data recovery.

Not supported

Other O&M Commands

To help you manage instances, GeminiDB Redis API provides O&M commands in specific scenarios.

Before running the following O&M commands, to avoid adverse impacts on services, you are advised to choose Service Tickets > Create Service Ticket in the upper right corner of the console and contact the customer service.

  • ROCKSCONF:

    Syntax: ROCKSCONF SETOPTION/ SETDBOPTION [Item] [Value]

    Function:

    • ROCKSCONF commands can adjust the RocksDB parameters of the storage engine to meet service requirements.
    • Item indicates a parameter to be adjusted and Value its value. For details, see the RocksDB documentation.
  • COMPACT:

    Syntax: COMPACT [Type] [Partition ID]

    Function:

    • COMPACT commands can effectively reduce RocksDB tombstones, improving read performance while reducing storage space.
    • type indicates the data type to be compacted. The value can be string, hash, zset, set, or list.
    • partition_id indicates a data shard for which COMPACT is to be executed. You can run info partitions to obtain shard information of the instance. For details, see Connecting to an Instance Using a Load Balancer Address (Recommended).
      As shown in Figure 1, 179b5efc712a506c is a valid partition ID.
      Figure 1 info partitions

Usage Notes

  • GeminiDB Redis API does not support RESP3. Redis Serialization Protocol (RESP) is used for communication between a Redis server and a client. Mainstream clients such as Jedis use RESP2 by default, which can be used to access a GeminiDB Redis instance.
  • GeminiDB Redis API 7.0 does not support functions.

Parent Topic: Development Reference