[ https://issues.apache.org/jira/browse/LUCENE-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717004#comment-16717004 ]
Karl Wright commented on LUCENE-8587: ------------------------------------- {quote} Maybe we should build the point here using the equivalent [lat, lon] {quote} [~ivera] No, that makes no sense. Polygons are never constructed using (x,y,z) coordinates; they are always constructed using lat/lon points and a planet model. If the lat/lons are the same you won't get different x,y,z points, period. So there's something else being done wrong, and I think the problem is probably the random number generator construction of the testpoint. The testpoint should *not* be included in the equals computation for that reason. I will commit a fix. > Self comparison bug in GeoComplexPolygon.equals method > ------------------------------------------------------ > > Key: LUCENE-8587 > URL: https://issues.apache.org/jira/browse/LUCENE-8587 > Project: Lucene - Core > Issue Type: Bug > Components: modules/spatial3d > Affects Versions: 7.1 > Reporter: Zsolt Gyulavari > Assignee: Karl Wright > Priority: Major > Attachments: LUCENE-8587.patch > > > GeoComplexPolygon.equals method checks equality with own testPoint1 field > instead of the other.testPoint1. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org