Help Center/ GeminiDB/ GeminiDB Redis API/ FAQs/ Database Usage/ Why Is the Cursor Length Returned by SCAN of GeminiDB Redis API Is Longer Than That of Open-Source Redis?
Updated on 2025-07-02 GMT+08:00

Why Is the Cursor Length Returned by SCAN of GeminiDB Redis API Is Longer Than That of Open-Source Redis?

Possible causes:

  • The encoding rule of cursors returned by GeminiDB Redis API is different from that of open-source Redis, so the cursor returned by GeminiDB Redis API is longer. The cursor usage and behavior of GeminiDB Redis API and open-source Redis are the same, so data can be correctly traversed by clients.
  • As the number of keys increases, the Redis cursor length grows longer as well. Therefore, the cursor length returned by GeminiDB Redis API is acceptable. After a SCAN command is executed, the returned cursors must be parsed as 64-bit unsigned integers. Failing to do so may cause parsing failures or incorrect results. If a database receives these incorrect results, error message "invalid cursor" will be reported.