Skip to content

Conversation

@arp242
Copy link
Contributor

@arp242 arp242 commented Sep 13, 2024

Previously it would just report:

status: 400, failed: [x_content_parse_exception], reason: [1:77] [bool] failed to parse field [filter]

Which is just not very helpful; no idea what's wrong here. I've noticed this with quite a few errors over the last few weeks. The real error is "hidden" in the RootCause, so add that to the Error():

status: 400, failed: [x_content_parse_exception], reason: [1:77] [bool] failed to parse field [filter]: [term] query doesn't support multiple fields, found [collection_id] and [entities]

Which is a bit long, but at least it has the actual error in there.

Previously it would just report:

	status: 400, failed: [x_content_parse_exception], reason: [1:77] [bool] failed to parse field [filter]

Which is just not very helpful; no idea what's wrong here. I've noticed
this with quite a few errors over the last few weeks. The real error is
"hidden" in the RootCause, so add that to the Error():

	status: 400, failed: [x_content_parse_exception], reason: [1:77] [bool] failed to parse field [filter]: [term] query doesn't support multiple fields, found [collection_id] and [entities]

Which is a bit long, but at least it has the actual error in there.
@arp242 arp242 closed this by deleting the head repository May 28, 2025
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

Successfully merging this pull request may close these issues.

1 participant