Renaming Commands of a GeminiDB Redis Instance

Scenarios

Running high-risk commands on a general-purpose GeminiDB Redis instance may cause data loss, instance restart, or performance fluctuation. You can rename high-risk commands to reduce misoperations and ensure data security and system stability.

Usage Notes

• To rename commands on instances of some earlier versions, you need to update them by following Upgrading a Minor Version.
• High-risk commands can be renamed only when your instance is in the Available state.
• Commands of a Redis Cluster instance cannot be renamed.

Procedure

1. Log in to the GeminiDB console.
2. On the Instances page, locate the target instance and choose More > Rename High-risk Command in the Operation column.
   Figure 1 Command renaming
   

3. Select the required commands and disable them. For involved parameters, see Table 1.

   Table 1 Parameter description

   Parameter	Description
   flushall	Clears all buffers.
   flushdb	Deletes all keys in the current database.
   hgetall	Returns all fields and values in the hash table.
   hkeys	Returns all keys in the hash table.
   hvals	Returns all values in the hash table.
   keys	Finds all keys that match a given pattern.
   smembers	Returns all members in a set. Any set without keys is considered empty.
   New Name	Name of the command that takes effect currently. The name can include 0 to 30 characters. Command names are case-insensitive and can contain only letters, digits, hyphens (-), and underscores (_). If the name is left blank, the command is disabled. The new name must be unique.
   Disabled	The Disabled option is toggled off by default. You can click to toggle on it. If a command is disabled, its new name is empty.

4. Modify parameter information and click OK.
   Figure 2 Renaming commands
   

5. Check the renaming result.
   • You can view new command names on the Rename High-risk Command page.
   • After the renaming is complete, original commands become invalid and you need to use new commands to perform operations.