-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
datasets query error #8211
Comments
It looks like you're encountering a "Cannot query field" error when trying to perform hit testing on your datasets. This issue is often caused by querying a field that is not defined in the dataset fields. Here are some common causes and solutions for this error:
Here is an example of correctly defined fields in dataset_query_detail_fields = {
"id": fields.String,
"content": fields.String,
"source": fields.String,
"source_app_id": fields.String,
"created_by_role": fields.String,
"created_by": fields.String,
"created_at": TimestampField,
} Ensure that the field Additionally, there are known issues or limitations with the
By addressing these potential issues, you should be able to resolve the error and successfully query your datasets. |
|
|
I think this is introduced in this pr #7749 |
No wonder, I tried the pdf file the hit-testing worked well, but the txt file failed. |
I think this is the root cause of the problem,i'm using weaviate DB as default DB |
remove the 'page' from attributes it will be solved. |
Self Checks
Dify version
0.8.0
Cloud or Self Hosted
Self Hosted (Source)
Steps to reproduce
After upgrading the version, some of my knowledge datasets cannot be queried!!!
And i try to create a new dataset and the same error occurred
1.creating a new dataset,and upload 1 file
2.try a hit testing
✔️ Expected Behavior
queried Successfully
❌ Actual Behavior
queried fail
The text was updated successfully, but these errors were encountered: