[ 
https://issues.apache.org/jira/browse/LUCENE-9580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17559043#comment-17559043
 ] 

ASF subversion and git services commented on LUCENE-9580:
---------------------------------------------------------

Commit 6a3f50539587cdabe5efe199bc06f6375f1d092a in lucene-solr's branch 
refs/heads/branch_8_11 from Hugo Mercier
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=6a3f5053958 ]

LUCENE-9580: Fix bug in the polygon tessellator when introducing collinear 
edges during polygon splitting (#2452) (#2664)

Co-authored-by: Ignacio Vera <iv...@apache.org>

> Tessellator failure for a certain polygon
> -----------------------------------------
>
>                 Key: LUCENE-9580
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9580
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: 8.5, 8.6
>            Reporter: Iurii Vyshnevskyi
>            Assignee: Ignacio Vera
>            Priority: Major
>             Fix For: 9.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> This bug was discovered while using ElasticSearch (checked with versions 
> 7.6.2 and 7.9.2).
> But I've created an isolated test case just for Lucene: 
> [https://github.com/apache/lucene-solr/pull/2006/files]
>  
> The unit test fails with "java.lang.IllegalArgumentException: Unable to 
> Tessellate shape".
>  
> The polygon contains two holes that share the same vertex and one more 
> standalone hole.
> Removing any of them makes the unit test pass. 
>  
> Changing the least significant digit in any coordinate of the "common vertex" 
> in any of two first holes, so that these vertices become different in each 
> hole - also makes unit test pass.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to