jpountz commented on PR #12162: URL: https://github.com/apache/lucene/pull/12162#issuecomment-1446752140
I agree we should have better ways to help users store these richer types, though ideally I'd like it to not fiddle with formatting, which feels like it may be a can of worms? Thinking out loud, what about storing the data with the same rounding that we enforce for the KD index and doc values, store lat/lon points as longs, and introduce helper methods to deal with stored data like we do for queries? E.g. something like `Point LatLonField#decode(long storedValue)`. Shapes could do something similar, e.g. `LatLonGeometry decode(BytesRef storedValue)`? -- 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. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
