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

Dynamic Selection of Knowledge Datasets in Knowledge Retrieval Nodes #3152

New Issue
Closed
opened 2026-02-21 17:54:23 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 17:54:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @Nazza77 on GitHub (May 10, 2024).

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).
  • Pleas do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

While developing a local ChatBot with long-term memory capabilities, I encountered a significant limitation concerning the management of knowledge datasets.
Each user must have a distinct dataset to maintain privacy and the relevance of interactions.

Currently, the selection of the dataset in the "Knowledge Retrieval" node is static and manual, which makes it impossible to automate the system for multiple users.

2. Describe the feature you'd like to see

I propose implementing a feature that allows dynamic selection of the "Knowledge Dataset" within the "Knowledge Retrieval" node.

This feature would involve using a variable, such as the knowledge dataset's ID, to automatically select the corresponding dataset.
This would enable the node to load and use the correct set of knowledge specific to each user during interactions.

3. How will this feature improve your workflow or experience?

This feature would transform the capability of the ChatBot to operate coherently and personally with multiple users, ensuring that each interaction is informed by the correct context and secure personal data.
Moreover, it would allow the product to scale without compromising data privacy or the relevance of the responses provided, which are essential for maintaining a high-quality user experience and compliance with privacy standards.

4. Additional context or comments

While developing a local ChatBot with long-term memory capabilities, I encountered a significant limitation concerning the management of knowledge datasets. Each user must have a distinct dataset to maintain privacy and the relevance of interactions. Currently, the selection of the dataset in the Knowledge Retrieval node is static and manual, which makes it impossible to automate the system for multiple users.

I would also like to extend my gratitude to the Dify team and the surrounding community for your hard work and dedication. Your commitment to developing such a high-quality solution is truly commendable. Keep up the great work! 😁

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Nazza77 on GitHub (May 10, 2024). ### 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] Pleas do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? While developing a local ChatBot with **long-term memory** capabilities, I encountered a significant limitation concerning the management of **knowledge datasets**. Each user must have a **distinct dataset** to maintain **privacy** and the **relevance** of interactions. Currently, the selection of the dataset in the "**Knowledge Retrieval**" node is **static** and **manual**, which makes it impossible to **automate** the system for **multiple users**. ### 2. Describe the feature you'd like to see I propose implementing a feature that allows **dynamic selection** of the "**Knowledge Dataset**" within the "Knowledge Retrieval" node. This feature would involve using a **variable**, such as the **knowledge dataset's ID**, to automatically select the corresponding dataset. This would enable the node to load and use the correct set of knowledge specific to each user during interactions. ### 3. How will this feature improve your workflow or experience? This feature would transform the capability of the ChatBot to **operate coherently** and **personally** with **multiple users**, ensuring that each interaction is informed by the correct **context** and secure **personal data**. Moreover, it would allow the product to scale without compromising data privacy or the relevance of the responses provided, which are essential for maintaining a high-quality user experience and compliance with privacy standards. ### 4. Additional context or comments While developing a local ChatBot with long-term memory capabilities, I encountered a significant limitation concerning the management of knowledge datasets. Each user must have a distinct dataset to maintain privacy and the relevance of interactions. Currently, the selection of the dataset in the **Knowledge Retrieval** node is static and manual, which makes it impossible to automate the system for multiple users. > I would also like to extend my gratitude to the Dify team and the surrounding community for your hard work and dedication. Your commitment to developing such a high-quality solution is truly commendable. Keep up the great work! 😁 ### 5. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 🌊 feat:workflow label 2026-02-21 17:54:23 -05:00
yindo closed this issue 2026-02-21 17:54:23 -05:00
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 🌊 feat:workflow
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#3152
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?