[ https://issues.apache.org/jira/browse/LUCENE-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709022#comment-16709022 ]
Nicholas Knize commented on LUCENE-8581: ---------------------------------------- {quote}Just for my curiosity. when creating a triangle in the tessellator points get order. is that really needed? what is the purpose? {quote} That can be removed. It's legacy from before the selective indexing approach was used. It sounds like that will solve a big part of the problem +1 for using 2^3 constants. And I also think we can continue to iterate on the readability part in a separate patch. I don't think it should hold up the bigger benefit of a smaller index. > Change LatLonShape encoding to use 4 BYTES Per Dimension > -------------------------------------------------------- > > Key: LUCENE-8581 > URL: https://issues.apache.org/jira/browse/LUCENE-8581 > Project: Lucene - Core > Issue Type: New Feature > Reporter: Nicholas Knize > Assignee: Ignacio Vera > Priority: Major > Attachments: LUCENE-8581.patch, LUCENE-8581.patch > > > {{LatLonShape}} tessellated triangles currently use a relatively naive > encoding with the first four dimensions as the bounding box of the triangle > and the last three dimensions as the vertices of the triangle. To encode the > {{x,y}} vertices in the last three dimensions requires {{bytesPerDim}} to be > set to 8, with 4 bytes for the x & y axis, respectively. We can reduce > {{bytesPerDim}} to 4 by encoding the index(es) of the vertices shared by the > bounding box along with the orientation of the triangle. This also opens the > door for supporting {{CONTAINS}} queries. -- 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