search

clearlydefined / operations

Operational documentation and tools
3 stars 10 forks source link

Triage Service exceptions: Cannot find fields enabled for suggestions. Provide 'suggesterName' in query. (/definitions) #35

Closed grvillic closed 2 years ago

grvillic commented 4 years ago

This is returning a 400 internally, but clients are getting a 500.

requests 
| where resultCode == 500
| join (
 exceptions
 ) on operation_Id 
| extend pathPrefix = extract("/(\\w+)", 0, tostring(operation_Name))
| summarize count() by  outerMessage, pathPrefix
| order by count_  desc 
| where outerMessage contains "Cannot find fields enabled for suggestions"
jcfiorenzano commented 4 years ago

This is happening if the search pattern includes the encoding %23 and IIS is interpreting that as a fragment ignoring the rest of the url parameters like suggesterName. I created a support item for Azure Search because this looks like an issue in their end.

https://github.com/clearlydefined/service/issues/727

nellshamrell commented 3 years ago

Hey @jcfiorenzano - did you ever hear back from Azure Support on this?