[ https://issues.apache.org/jira/browse/LUCENE-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253292#comment-15253292 ]
Karl Wright commented on LUCENE-7240: ------------------------------------- +1 This looks like a big help (and will unblock my work too). > Remove DocValues from LatLonPoint, add DocValuesField for that > -------------------------------------------------------------- > > Key: LUCENE-7240 > URL: https://issues.apache.org/jira/browse/LUCENE-7240 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Robert Muir > Attachments: LUCENE-7240.patch, LUCENE-7240.patch > > > LatLonPoint needed two-phase intersection initially because of big > inefficiencies, but as of LUCENE-7239 all of its query operations: > {{newBoxQuery()}}, {{newDistanceQuery()}}, {{newPolygonQuery()}} and > {{nearest()}} only need the points datastructure (BKD). > If you want to do {{newDistanceSort()}} then you need docvalues for that, but > I think it should be moved to a separate field: e.g. docvalues is optional > just like any other field in lucene. We can add other methods that make sense > to that new docvalues field (e.g. facet by distance/region, expressions > support, whatever). It is really disjoint from the core query support: and > also currently has a heavyish cost of ~64-bits per value in space. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org