You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2015/11/20 12:31:11 UTC
[jira] [Commented] (LUCENE-6904) Rewrite max bound
GeoPointInBBoxQuery to FieldValueQuery
[ https://issues.apache.org/jira/browse/LUCENE-6904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15015635#comment-15015635 ]
Michael McCandless commented on LUCENE-6904:
--------------------------------------------
+1, except maybe add a comment where you use {{FieldValueQuery}} explaining that we can do this because we index the lat/lon into doc values?
> Rewrite max bound GeoPointInBBoxQuery to FieldValueQuery
> --------------------------------------------------------
>
> Key: LUCENE-6904
> URL: https://issues.apache.org/jira/browse/LUCENE-6904
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: Trunk, 5.4
> Reporter: Nicholas Knize
> Priority: Minor
> Attachments: LUCENE-6904.patch, LUCENE-6904.patch
>
>
> This simple improvement rewrites a GeoPointInBBoxQuery to a FieldValueQuery when the min/max lon/lat (or x/y) values are set to their limits (e.g., -180, 180, -90, 90). This bypasses all unnecessary GeoPointTermsEnum logic.
--
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