You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Nicholas Knize (JIRA)" <ji...@apache.org> on 2016/06/17 21:14:05 UTC
[jira] [Updated] (LUCENE-7343) Cleanup GeoPoint Query
implementation
[ https://issues.apache.org/jira/browse/LUCENE-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas Knize updated LUCENE-7343:
-----------------------------------
Attachment: LUCENE-7343.patch
First iteration patch:
* Eliminates dead code from {{GeoPointTermsEnum}} left over from the legacy numeric implementation
* Simplifies {{CellComparator}} by squashing separate {{within}}, {{crosses}} methods into a single {{relate}} method
* {{GeoPointDistanceQuery}} uses haversine {{sortKey}} approach similar to {{LatLonPointDistanceQuery}}
> Cleanup GeoPoint Query implementation
> -------------------------------------
>
> Key: LUCENE-7343
> URL: https://issues.apache.org/jira/browse/LUCENE-7343
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nicholas Knize
> Attachments: LUCENE-7343.patch
>
>
> This is a cleanup task to simplify and trim dead code from GeoPointField's query classes. Much of the relation logic in {{LatLonPoint}} can also be applied to GeoPointField's {{CellComparator}} class eliminating the need to carry its own separate relation methods.
--
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