iverase commented on issue #927: LUCENE-8997: : Add type of triangle info to ShapeField encoding URL: https://github.com/apache/lucene-solr/pull/927#issuecomment-570509185 @jpountz of course, this is my logic. Considering two versions of Lucene X.Y and X.Z where Z > Y and with the current ShapeField formats: X.Y: Three first bits are the triangle type, next three bits are the edges features (current format) X.Z: Four first bits are the triangle type (including point and lines) and the next three bits are the edges features (new format). I consider it is possible to have an index created with X.Y and at some point in time this index is starting getting written by X.Z (user has upgraded the Lucene version). At some point merging might happen so we might end up with versions with points in different encoding in the same segment. In this case, the encoding needs to tells us which format it contains, does it make sense?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
