Open DmitriyShcherbina opened 1 year ago
In the code I see we doesn't even start the second part when "runMatchPrediction" is false: https://github.com/Anthony-Nolan/Atlas/blob/master/Atlas.Functions/DurableFunctions/Search/Client/SearchClientFunctions.cs#L40
Checked AN Atlas search requests - all of them have "runMatchPrediction": false, so we definitely need a fix for this issue
This is a known issue - AN Atlas Search checks matching-algorithm-results blob container, so this is OK for now.
This is not a bug per se, but an intentional design choice, though admittedly not so intuitive, and so could be revisited in future.
Steps to reproduce:
"runMatchPrediction": false
atlas-search-results
blob containerActual Result: Search results file is absent in
atlas-search-results
blob container in case of Search reqiest with"runMatchPrediction": false
But search results file presents inmatching-algorithm-results
blob containerExpected Result: Search results file presents in
atlas-search-results
blob container in case of Search reqiest with"runMatchPrediction": false