langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Support metadata-based search in knowledge base API #11946

New Issue
Closed
opened 2026-02-21 19:04:53 -05:00 by yindo · 11 comments
yindo commented 2026-02-21 19:04:53 -05:00
Owner
Copy Link
Copy Source

Originally created by @liangliang4ward on GitHub (Mar 21, 2025).

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.

Currently, the knowledge base API only supports text-based searches, but it would be highly beneficial to enable searching via metadata fields.

Feature Request:

Add support for querying knowledge base items using metadata attributes (e.g., tags, creation date, author, file type).
Provide a flexible query mechanism that allows combining full-text and metadata searches.
Ensure efficient indexing to maintain performance.
Use Case:
Users need to filter knowledge base entries based on metadata attributes instead of only relying on text search. For instance, retrieving all PDFs uploaded in the last 30 days or searching for documents tagged with "compliance".

Looking forward to your consideration!

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @liangliang4ward on GitHub (Mar 21, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] 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. Currently, the knowledge base API only supports text-based searches, but it would be highly beneficial to enable searching via metadata fields. Feature Request: Add support for querying knowledge base items using metadata attributes (e.g., tags, creation date, author, file type). Provide a flexible query mechanism that allows combining full-text and metadata searches. Ensure efficient indexing to maintain performance. Use Case: Users need to filter knowledge base entries based on metadata attributes instead of only relying on text search. For instance, retrieving all PDFs uploaded in the last 30 days or searching for documents tagged with "compliance". Looking forward to your consideration! ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 19:04:53 -05:00
yindo closed this issue 2026-02-21 19:04:53 -05:00
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@gemchen commented on GitHub (Mar 21, 2025):

according to the dev logs:
version 1.1.0 already support metadata filter.

BUT, I tried the filter in the workflow, it's not work as in the blog. E.g. I set a filter with “document_name” start with "xxx", it still retrival all docs.

@gemchen commented on GitHub (Mar 21, 2025): according to the [dev logs](https://dify.ai/blog/dify-v1-1-0-filtering-knowledge-retrieval-with-customized-metadata): version 1.1.0 already support metadata filter. BUT, I tried the filter in the workflow, it's not work as in the blog. E.g. I set a filter with “document_name” start with "xxx", it still retrival all docs.
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@liangliang4ward commented on GitHub (Mar 21, 2025):

according to the dev logs: version 1.1.0 already support metadata filter.

BUT, I tried the filter in the workflow, it's not work as in the blog. E.g. I set a filter with “document_name” start with "xxx", it still retrival all docs.

Although the knowledge base node already supports metadata filtering, the API has not yet supported it.

@liangliang4ward commented on GitHub (Mar 21, 2025): > according to the [dev logs](https://dify.ai/blog/dify-v1-1-0-filtering-knowledge-retrieval-with-customized-metadata): version 1.1.0 already support metadata filter. > > BUT, I tried the filter in the workflow, it's not work as in the blog. E.g. I set a filter with “document_name” start with "xxx", it still retrival all docs. Although the knowledge base node already supports metadata filtering, the API has not yet supported it.
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 21, 2025):

What's your version? We have a bunch of fixes related to this one https://github.com/langgenius/dify/pulls?q=is%3Apr+author%3AJohnJyong+is%3Aclosed

@crazywoola commented on GitHub (Mar 21, 2025): What's your version? We have a bunch of fixes related to this one https://github.com/langgenius/dify/pulls?q=is%3Apr+author%3AJohnJyong+is%3Aclosed
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@liangliang4ward commented on GitHub (Mar 23, 2025):

What's your version? We have a bunch of fixes related to this one https://github.com/langgenius/dify/pulls?q=is%3Apr+author%3AJohnJyong+is%3Aclosed

Image this api need support metadata serach

@liangliang4ward commented on GitHub (Mar 23, 2025): > What's your version? We have a bunch of fixes related to this one https://github.com/langgenius/dify/pulls?q=is%3Apr+author%3AJohnJyong+is%3Aclosed ![Image](https://github.com/user-attachments/assets/a91d137f-d38b-4c13-bff5-bc1623b3d2df) this api need support metadata serach
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@JulyMood commented on GitHub (Mar 27, 2025):

+1

@JulyMood commented on GitHub (Mar 27, 2025): +1
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@kamtang0823 commented on GitHub (Mar 27, 2025):

+1

@kamtang0823 commented on GitHub (Mar 27, 2025): +1
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@yathaarthmagi commented on GitHub (Mar 28, 2025):

+1, without this the api is insufficient.

@yathaarthmagi commented on GitHub (Mar 28, 2025): +1, without this the api is insufficient.
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@yathaarthmagi commented on GitHub (Mar 29, 2025):

Just wanted to know whether this addition to the knowledge api is planned ? The knowledge base features provided by dify are great, however, without metadata filtering in the search api, it will not for work for us! Really hope that gets added in the near future!

@yathaarthmagi commented on GitHub (Mar 29, 2025): Just wanted to know whether this addition to the knowledge api is planned ? The knowledge base features provided by dify are great, however, without metadata filtering in the search api, it will not for work for us! Really hope that gets added in the near future!
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@loshaless commented on GitHub (Apr 1, 2025):

+1

@loshaless commented on GitHub (Apr 1, 2025): +1
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@yathaarthmagi commented on GitHub (Apr 17, 2025):

Is this on the cards ?

@yathaarthmagi commented on GitHub (Apr 17, 2025): Is this on the cards ?
yindo commented 2026-02-21 19:04:54 -05:00
Author
Owner
Copy Link
Copy Source

@JulesFonsecaDiiage commented on GitHub (Apr 17, 2025):

+1

@JulesFonsecaDiiage commented on GitHub (Apr 17, 2025): +1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#11946
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?