Multi-Valued Index Hopes to Utilize Prefix Index Functionality

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 多值索引希望可使用前缀索引功能

| username: Hacker_ojLJ8Ndr

Requirement Feedback
Please clearly and accurately describe the problem scenario, required behavior, and background information to help the product team follow up on the requirement promptly.
[Problem Scenario Involved in the Requirement]
When creating a multi-valued index for a varchar+json array, during usage, if the varchar column is empty and the json array is empty, using the condition where the varchar column is empty cannot retrieve data.
Documentation annotation:

[Expected Required Behavior]
When the above situation occurs, can the following behaviors be supported:

  1. The execution plan avoids using the multi-valued index and correctly retrieves the data.
  2. The multi-valued index supports prefix index query functionality.

[Alternative Solutions for the Requirement]

[Background Information]
Such as which users will benefit from it, and some usage scenarios. Any API design, model, or diagram would be more helpful.

| username: Billmay表妹 | Original post link

The PM is currently researching this requirement.

| username: Roger_Song | Original post link

Can you provide a simple example, including your case and expectations?