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

The retrieval method of the knowledge base cannot be modified #4384

Open
4 tasks done
leoterry-ulrica opened this issue May 14, 2024 · 3 comments
Open
4 tasks done

The retrieval method of the knowledge base cannot be modified #4384

leoterry-ulrica opened this issue May 14, 2024 · 3 comments

Comments

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

Dify version

0.6.8

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • When I create an empty repository and want to modify the retrieval method, I am not allowed to modify it.

8d14bf3145572d62baef1e5aff66bff

✔️ Expected Behavior

It is hoped that the search method can be modified.

❌ Actual Behavior

No response

Copy link

dosubot bot commented May 14, 2024

To address the issue with modifying the retrieval method in Dify version 0.6.8, ensure your Docker environment is correctly set up with the required versions and resources. Verify that all Dify configuration settings, especially those related to the vector database and retrieval methods, are correctly applied. This includes checking environment variables like VECTOR_STORE, WEAVIATE_ENDPOINT, and similar settings crucial for data retrieval configurations.

If the problem persists, consider upgrading Dify to the latest version and reviewing the application's documentation for any specific configuration steps related to the retrieval method. The error message "请按照要求配置信息" indicates a configuration issue, so double-checking the settings against the documentation might help resolve the problem.

For modifying the retrieval method, navigate to the dataset settings within Dify and adjust the "Retrieval Settings" as needed for your application. If these steps do not resolve the issue, utilize Dify's debugging tools and error logs for further troubleshooting.

This approach should help in resolving the configuration issue and allow you to modify the retrieval method as expected.

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

@leoterry-ulrica
Copy link
Author

To address the issue with modifying the retrieval method in Dify version 0.6.8, ensure your Docker environment is correctly set up with the required versions and resources. Verify that all Dify configuration settings, especially those related to the vector database and retrieval methods, are correctly applied. This includes checking environment variables like VECTOR_STORE, WEAVIATE_ENDPOINT, and similar settings crucial for data retrieval configurations.

If the problem persists, consider upgrading Dify to the latest version and reviewing the application's documentation for any specific configuration steps related to the retrieval method. The error message "请按照要求配置信息" indicates a configuration issue, so double-checking the settings against the documentation might help resolve the problem.

For modifying the retrieval method, navigate to the dataset settings within Dify and adjust the "Retrieval Settings" as needed for your application. If these steps do not resolve the issue, utilize Dify's debugging tools and error logs for further troubleshooting.

This approach should help in resolving the configuration issue and allow you to modify the retrieval method as expected.

Details

Sources

About Dosu This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

Answering the wrong question won't solve the problem!!!

Copy link

dosubot bot commented May 15, 2024

To resolve the issue with modifying the retrieval method in Dify version 0.6.8, follow these targeted steps:

  1. Check Re-Rank Model Selection: Ensure a valid re-rank model is selected. The error might stem from a missing selection in this area.

  2. Update Retrieval Configuration: Adjust your retrieval method settings using setRetrievalConfig. This is crucial when changing between different retrieval methods like "high_quality" and "economical".

  3. Save Configuration: Use handleSave to apply your changes. This function checks for the necessary configurations, including the re-rank model, before saving.

  4. Review Error Messages: If errors persist, the specific error message provided during the save attempt will guide you to the missing or incorrect configuration.

  5. Ensure All Required Fields Are Completed: Particularly, the dataset name and re-rank model selection are critical for a successful configuration update.

  6. Permissions and Index Method: Verify that settings related to permissions and the index method align with your requirements.

For environment variables like VECTOR_STORE and WEAVIATE_ENDPOINT, ensure they are correctly set for your Docker setup. These are essential for configuring the vector database and retrieval methods.

For detailed guidance, refer to the Dify documentation and the Dify repository. If the issue remains unresolved, consulting the support community with your specific setup details might provide further assistance.

Details

Sources


About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

To continue the conversation, mention @dosu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant