You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, polygon searches for geospatial query supported by existing Redis are not available.
To perform a polygon search, as I understand it, you would need to receive multiple latitude and longitude coordinates to define the boundary, and then search for desired objects such as taxi, convenience stores, parking lots, etc. within that boundary.
We have confirmed that while MemoryDB for Valkey supports FT.SEARCH, it does not support polygon searches. (GEO, GEOSHAPE)
We have confirmed that vector search(eg.FT.search) and radius search(geoadd, geosearch) is available but it couldn't fulfill customer's requirement.
Description of the feature
Valkey would allow polygon search in native feature
Alternatives you've considered
Using Redis cloud
Additional information
Any additional information that is relevant to the feature request.
The text was updated successfully, but these errors were encountered:
The problem/use-case that the feature addresses
Currently, polygon searches for geospatial query supported by existing Redis are not available.
To perform a polygon search, as I understand it, you would need to receive multiple latitude and longitude coordinates to define the boundary, and then search for desired objects such as taxi, convenience stores, parking lots, etc. within that boundary.
We have confirmed that while MemoryDB for Valkey supports FT.SEARCH, it does not support polygon searches. (GEO, GEOSHAPE)
We have confirmed that vector search(eg.FT.search) and radius search(geoadd, geosearch) is available but it couldn't fulfill customer's requirement.
Description of the feature
Valkey would allow polygon search in native feature
Alternatives you've considered
Using Redis cloud
Additional information
Any additional information that is relevant to the feature request.
The text was updated successfully, but these errors were encountered: