[
https://issues.apache.org/jira/browse/LUCENE-8587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717020#comment-16717020
]
Karl Wright commented on LUCENE-8587:
-------------------------------------
Ok, you're right, this is more complex. We cannot do without the testpoint and
the in/out of set boolean, even though moving these around might produce
exactly the same polygon.
On the other hand, blaming the serialization of the testpoint also seems odd
since it's basically preserved from the constructor in whatever form was there.
Perhaps serialization/deserialization of the geopoint needs to change. Let me
examine that next.
> 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: [email protected]
For additional commands, e-mail: [email protected]
