You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2016/04/22 02:30:13 UTC

[jira] [Created] (LUCENE-7240) Remove DocValues from LatLonPoint, add DocValuesField for that

Robert Muir created LUCENE-7240:
-----------------------------------

             Summary: 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


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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org