Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dify could not recall the contents of the economical files in the recall test of the knowledge base #8403

Closed
5 tasks done
First-fan opened this issue Sep 14, 2024 · 1 comment
Labels
🐞 bug Something isn't working stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed

Comments

@First-fan
Copy link

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.8.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

dify could not recall the contents of the economical files in the recall test of the knowledge base
image
image
Even if I copied the contents of the file directly to test it, I could not recall it

✔️ Expected Behavior

Economical knowledge base files can be recalled successfully for testing

❌ Actual Behavior

Economical knowledge base files can be recalled for test failure

Copy link

dosubot bot commented Sep 14, 2024

There are similar issues that have been reported and resolved:

  1. Generate an empty response after importing Knowledge (closed):

    • Solution: Ensure the data import process is complete and correct. Verify the model selection and configuration, especially for language support. Check application settings related to AI commands and context. Consider version-specific issues and updates [1].
  2. Full-Text Search problem (closed):

    • Solution: Configure Weaviate to use an appropriate vectorizer module. Update the docker-compose.yml file to include the vectorizer module and restart the Docker containers [2].

For your specific issue with the Economical indexing mode in version 0.8.0, the problem lies in the indexing method used. The Economical mode employs an offline vector engine and keyword indexing, which reduces accuracy. The retrieval setting is limited to Inverted Index, which may not be as effective in recalling relevant text segments compared to other methods like High-Quality mode [3][4].

Additionally, specific error messages like "no se pudieron indexar los documentos" (documents could not be indexed) are generated when the Economical indexing mode fails to recall documents [5].

To improve recall accuracy, consider using a different indexing mode, such as High-Quality mode, which utilizes more advanced retrieval methods.

To continue talking to Dosu, mention @dosu.

@dosubot dosubot bot added the 🐞 bug Something isn't working label Sep 14, 2024
@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
Projects
None yet
Development

No branches or pull requests

2 participants