nknize commented on issue #11702: URL: https://github.com/apache/lucene/issues/11702#issuecomment-1294232828
My muscle memory (and gmail filters) is stuck at jira :) So I missed these. > The use-case here is also not great, talking about a doc having multiple locations Curious why you think a document can't have multiple locations? Why wouldn't the geo (wkt, json, wkb, protobuf) specification then not have Multi geometry types? The reason they do is because multi location can exist for a single document. It happens all the time, especially in data science applications where multiple observations are collected concurrently in a single document scan (RADAR, Multi Hypothesis Tracking). I should be able to have a multi value doc value for running facets, aggregations, spark jobs over the data stored in the lucene segment instead of trying to hack together a single encoding that stores all of the observations at once, and then post filter after decoding that entire binary value. > while mostly providing syntactic sugar for users. Except in the case of shape doc values this isn't syntactic sugar. The way the centroid is computed for a multi value shape is based on weighted area of the individual geometries, and in this case the way the centroid is computed and stored in a shape doc value for a multi shape geometry is a hack because of this limitation. Assuming this is syntactic sugar just feels like a lazy way -- 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
