Is your feature request related to a problem? Please describe.
The Reporter always returns a 422 on receiving a geo query with an NGSI SLF equals operator---have a look at the geo_query_handler module. This is because geo queries were only supported by the Crate backend and a bug in Crate results in the equals operator not working properly---see #120 about it. As of PR #374 we've had a fully functional implementation of geo queries in the Timescale backend, including equality queries. The Reporter should take this into account and let clients use the equals operator if the query targets the Timescale backend.
Describe the solution you'd like
Change the geo_query_handler module so it lets equality queries go through if they target Timescale whereas still returning a 422 if the backend is Crate. Update the test_geo* modules accordingly so that in the case of Timescale we check equality works!
github-actions[bot]
commented
3 years ago
Is your feature request related to a problem? Please describe.
The Reporter always returns a
422on receiving a geo query with an NGSI SLFequalsoperator---have a look at thegeo_query_handlermodule. This is because geo queries were only supported by the Crate backend and a bug in Crate results in theequalsoperator not working properly---see #120 about it. As of PR #374 we've had a fully functional implementation of geo queries in the Timescale backend, including equality queries. The Reporter should take this into account and let clients use theequalsoperator if the query targets the Timescale backend.Describe the solution you'd like
Change the
geo_query_handlermodule so it lets equality queries go through if they target Timescale whereas still returning a422if the backend is Crate. Update thetest_geo*modules accordingly so that in the case of Timescale we check equality works!Describe alternatives you've considered
N/A
Additional context
See #374, #120.