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

The "reranking_enable" field is preventing the re-ranking model from being enabled for the multi-knowledge base search. #18036

New Issue
Closed
opened 2026-02-21 19:42:48 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:42:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @oDoubleyz on GitHub (Sep 23, 2025).

Originally assigned to: @WTW0313 on GitHub.

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, 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.

Dify version

1.8.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I have configured the retrieval of multiple knowledge bases and set up the use of a re-ranking model at the end. However, I noticed that even though I enabled the re-ranking model, the field reranking_enable was set to false by the frontend, which prevented the re-ranking model from being used for secondary sorting.

Image Image

✔️ Expected Behavior

Can use the re-ranking model correctly.

❌ Actual Behavior

No response

Originally created by @oDoubleyz on GitHub (Sep 23, 2025). Originally assigned to: @WTW0313 on GitHub. ### 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 bug report, 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. ### Dify version 1.8.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I have configured the retrieval of multiple knowledge bases and set up the use of a re-ranking model at the end. However, I noticed that even though I enabled the re-ranking model, the field `reranking_enable` was set to false by the frontend, which prevented the re-ranking model from being used for secondary sorting. <img width="1586" height="764" alt="Image" src="https://github.com/user-attachments/assets/a6f5cee5-78d7-4f5e-9849-81f1844bc081" /> <img width="1205" height="662" alt="Image" src="https://github.com/user-attachments/assets/1e343e0a-d3ec-4841-abbf-0c03a7af6c41" /> ### ✔️ Expected Behavior Can use the re-ranking model correctly. ### ❌ Actual Behavior _No response_
yindo added the 👻 feat:rag label 2026-02-21 19:42:48 -05:00
yindo closed this issue 2026-02-21 19:42:48 -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:rag
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#18036
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?