Describe the bug
For /search/location/query when disable_fuzziness: true it still produces response that do not match the exact query.
We need to decide expected behavior in this particular route.
To Reproduce
Steps to reproduce the behavior:
- run the project.
- send request to
/search/location/query with disable_fuzziness: true and a query that won't produce exact match like airport. For example:
curl --location 'http://localhost:8080/search/location/query?query=airport%2C%20los%20angele&disable_fuzziness=true'
Expected behavior
For the example above, i'm not sure if we should produce a result.
Additional context
Currently, the query is based on ElasticSearch's function_score. If we want to really support disable_fuzziness: true, we need to rewrite the query mechanism.
Describe the bug
For
/search/location/querywhendisable_fuzziness: trueit still produces response that do not match the exact query.We need to decide expected behavior in this particular route.
To Reproduce
Steps to reproduce the behavior:
/search/location/querywithdisable_fuzziness: trueand a query that won't produce exact match likeairport. For example:Expected behavior
For the example above, i'm not sure if we should produce a result.
Additional context
Currently, the query is based on ElasticSearch's
function_score. If we want to really supportdisable_fuzziness: true, we need to rewrite the query mechanism.