Query stopped working on Azure Cognitive Search Index

Jason Herron 0

Has anyone had problems with the Search Explorer tab on an Azure Index?

Jason Herron 0 Reputation points

2023-11-21T16:00:46.94+00:00
Maybe a little more info would be helpful....

None of the search parameters are being followed

"count=true" does not return a count

defined fields with "select=" is not being respected -- all fields are coming back

Other custom fields used for filtering are not being respected.

I have been running the same query daily for the past month. It started breaking around 11/14/2023 with no changes to what I was using.
brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-11-22T23:56:06.2933333+00:00

Can you please provide more information about the query you're running? Specifically, can you share the query syntax and any filters you're using? Additionally, have you made any changes to your index schema or data source recently? This information will help me better understand the issue and provide you with a more accurate solution.

The more information you provide us, the better we can assist you.
Jason Herron 0 Reputation points

2023-11-27T16:09:51.6033333+00:00

Thank you for checking in. I figured this out.

It appears that you can no longer use anything but the "search" field in the "Query view" text box. I found this by switching to the JSON view and saw that the configuration looked different. 1) It was stuffing my entire query into the "search" field (including count, select, filters, etc) and 2) adding some extra fields as well.

After converting my http query into JSON and using the JSON view, I got the expected results!

1 answer

Jason Herron 0 Reputation points

2023-11-27T16:14:10.2233333+00:00

It appears that you can no longer use anything but the "search" field in the "Query view" text box. Previously the Query view allowed you to have a query string type syntax. For example: search={search criteria}&searchMode=all&select={fields}&filter={filters}&count=true&orderby={order by}

I found this by switching to the JSON view and saw that the configuration looked different. 1) It was stuffing my entire query into the "search" field and 2) adding some extra fields as well.

After converting my http query into JSON and using the JSON view, I got the expected results!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment