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
FT.SEARCH looks to have limitations to find points contained for Polygons with big number values of vertices (Redis Enterprise Software release notes 7.2.4-52 August 2023)
#149
Closed
agrimaldi72 opened this issue
Apr 26, 2024
· 6 comments
I created a hash set for geoshape polygon (square) where vertices values are around 10000000
HSET shape:6 t "this is in my house" g "POLYGON((10000000 10000000, 15000000 10000000, 15000000 30000000, 10000000 30000000, 10000000 10000000))"
I tried FT.SEARCH and I didn't get expected result (it didn't get any polygon, I expected to see shape:6)
FT.SEARCH polygon_idx "@g:[CONTAINS $point]" PARAMS 2 point 'POINT(10000002 10000002)' DIALECT 3
I overwrote shape:6 to have vertices with lower numbers
HSET shape:6 t "this is in my house" g "POLYGON((1000000 1000000, 1500000 1000000, 1500000 3000000, 1000000 3000000, 1000000 1000000))"
I tried FT.SEARCH again and I got expected result (it got shape:6)
I overwrote shape:6 to have a very small square with big number value for vertices in order to lower amount of points and I got no polygon (same as depicted in point 3)
HSET shape:6 t "this is in my house" g "POLYGON((10000000 10000000, 10000010 10000000, 10000010 10000010, 10000000 10000010, 10000000 10000000))"
FT.SEARCH polygon_idx "@g:[CONTAINS $point]" PARAMS 2 point 'POINT(10000002 10000002)' DIALECT 3
Scenario:
Running Redis Enterprise Server deployed from RHOCP Operator
Those big numbers for vertices came from trying to use datum Campo Inchauspe for geo
The text was updated successfully, but these errors were encountered:
Hi thank you for this report, do you have a documentation request? Happy to help if you can give a bit more information about what you need (an answer or an update to he documentation?) You can also use Redis Co-Pilot to ask your question here https://redis.io/chat or refer to https://redis.io/docs/latest/develop/data-types/geospatial/
I posted the comment as a potential issue (unexpected behaviour), neither documentation nor copilot gave me hints about ft.search specific limitations regarding maximum values to use within geoshape polygons.
We should guide him to open a ticket on the RediSearch repo, providing the details steps to reproduce the bug Em 8 de mai. de 2024, à(s) 18:08, David Dougherty ***@***.***> escreveu:
Hey @adrianoamaral ... do you know or can you find out what the limit is for polygon points as related to search?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
Description:
HSET shape:6 t "this is in my house" g "POLYGON((10000000 10000000, 15000000 10000000, 15000000 30000000, 10000000 30000000, 10000000 10000000))"
FT.SEARCH polygon_idx "@g:[CONTAINS $point]" PARAMS 2 point 'POINT(10000002 10000002)' DIALECT 3
HSET shape:6 t "this is in my house" g "POLYGON((1000000 1000000, 1500000 1000000, 1500000 3000000, 1000000 3000000, 1000000 1000000))"
HSET shape:6 t "this is in my house" g "POLYGON((10000000 10000000, 10000010 10000000, 10000010 10000010, 10000000 10000010, 10000000 10000000))"
FT.SEARCH polygon_idx "@g:[CONTAINS $point]" PARAMS 2 point 'POINT(10000002 10000002)' DIALECT 3
Scenario:
Running Redis Enterprise Server deployed from RHOCP Operator
Those big numbers for vertices came from trying to use datum Campo Inchauspe for geo
The text was updated successfully, but these errors were encountered: