In Didy1.13.3, when searching the knowledge base, it seems like metadata filtering isn't working.

[Spell-maker-Y]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• 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 set up the metadata for the documents and made sure that the metadata for each document was set successfully, but when I searched, I found that the metadata filter didn't work.
I used the following search query, and the result is that the course_id is 42, not 37.
{
"query": "Recall similar historical six-dimensional scores, weak point risks, upper and lower limb analysis, overall conclusions, doctor's advice, and training suggestions, focusing on cardiovascular endurance, explosive power, flexibility, trunk control, upper and lower limb coordination, and compensation risks.",
"retrieval_model": {
"search_method": "semantic_search",
"reranking_enable": false,
"top_k": 3,
"score_threshold_enabled": false,
"metadata_filtering_conditions": {
"logical_operator": "and",
"conditions": [
{
"name": "course_id",
"comparison_operator": "is",
"value": "37"
}
]
}
}
}

2. Additional context or comments

[dosubot[bot]]

Hi @Spell-maker-Y! I'm Dosu and I'm helping the Dify team.

This matches a bug fixed in v1.14.1 by PR #35700. Your placement of metadata_filtering_conditions inside retrieval_model is correct. In v1.13.3, the request schema omits that field, so validation silently removes the filter before retrieval. That explains why a document with course_id: 42 can still be returned. [1] [2]

Upgrade to a release containing that fix, then retry the same request. The v1.14.1 release notes and upgrade guide explicitly include it; follow the documented backup and migration steps for your deployment. Moving the filter elsewhere in the JSON won't address this schema bug. [3] [2]

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.