Set the top k for knowledge base retrieval to be greater than 10 #22120

Closed
opened 2026-02-21 20:15:51 -05:00 by yindo · 1 comment
Owner

Originally created by @gcc-debug on GitHub (Feb 6, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Description

Set the top k for knowledge base retrieval to be greater than 10

Motivation

Customer environment requirements

Additional Context

No response

Originally created by @gcc-debug on GitHub (Feb 6, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for refactors or chores; if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Description Set the top k for knowledge base retrieval to be greater than 10 ### Motivation Customer environment requirements ### Additional Context _No response_
yindo added the 💪 enhancement label 2026-02-21 20:15:51 -05:00
yindo closed this issue 2026-02-21 20:15:51 -05:00
Author
Owner

@crazywoola commented on GitHub (Feb 6, 2026):

Hi @gcc-debug, thanks for opening this issue.

Why this is being closed

  • This feature request does not provide enough detail to evaluate or prioritize (the use case and expected value are too vague).
  • It lacks concrete context such as an example workflow, data scale, or the exact limit you need and why 10 is insufficient.

Next steps

  • Please open a new issue with a clear use case/scenario, example inputs or workflow, the desired limit, and why that limit is required. This will help us assess feasibility and impact.
@crazywoola commented on GitHub (Feb 6, 2026): Hi @gcc-debug, thanks for opening this issue. ### Why this is being closed - This feature request does not provide enough detail to evaluate or prioritize (the use case and expected value are too vague). - It lacks concrete context such as an example workflow, data scale, or the exact limit you need and why 10 is insufficient. ### Next steps - Please open a new issue with a clear use case/scenario, example inputs or workflow, the desired limit, and why that limit is required. This will help us assess feasibility and impact.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22120