You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
I've been working with knowledge retrieval and need to filter documents based on select variables. Currently, only string, number and time variables appear in the metadata filtering dropdown, while select variables are completely absent despite being functionally equivalent to strings at runtime. This prevents me from creating filters that use dropdown selection variables, which are essential for my use case.
2. Additional context or comments
The metadata filtering UI correctly shows string-type variables but ignores select-type variables, even though they could be treated identically for filtering purposes. I believe that this requires modifying the MetadataFilteringVariableType enum to include 'select' and updating the relevant components to handle select variables properly.
3. Can you help us with this feature?
I am interested in contributing to this feature.
The text was updated successfully, but these errors were encountered:
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
I've been working with knowledge retrieval and need to filter documents based on select variables. Currently, only string, number and time variables appear in the metadata filtering dropdown, while select variables are completely absent despite being functionally equivalent to strings at runtime. This prevents me from creating filters that use dropdown selection variables, which are essential for my use case.
2. Additional context or comments
The metadata filtering UI correctly shows string-type variables but ignores select-type variables, even though they could be treated identically for filtering purposes. I believe that this requires modifying the MetadataFilteringVariableType enum to include 'select' and updating the relevant components to handle select variables properly.
3. Can you help us with this feature?
The text was updated successfully, but these errors were encountered: