[
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965540#action_12965540
]
Yonik Seeley commented on LUCENE-2139:
--------------------------------------
bq. As far as I understand the spatial search is done by two range queries ANDed
Yep - but they are normally tri-range (i.e. Lucene Numeric) ranges, so pretty
efficient anyway.
>From what I saw of the existing tier code, I can't say that it would have been
>more efficient... and I can say that at least for some spatial queries, it
>would have been less efficient (since it always seemed to use one tier level
>for a query, not multiple).
> Cleanup and Improvement of Spatial Contrib
> ------------------------------------------
>
> Key: LUCENE-2139
> URL: https://issues.apache.org/jira/browse/LUCENE-2139
> Project: Lucene - Java
> Issue Type: Improvement
> Components: contrib/spatial
> Affects Versions: 3.1
> Reporter: Chris Male
> Assignee: Simon Willnauer
> Attachments: LUCENE-2139-Java5Only.patch, LUCENE-2139-svnScript.sh,
> LUCENE-2139.patch
>
>
> The current spatial contrib can be improved by adding documentation, tests,
> removing unused classes and code, repackaging the classes and improving the
> performance of the distance filtering. The latter will incorporate the
> multi-threaded functionality introduced in LUCENE-1732.
> Other improvements involve adding better support for different distance
> units, different distance calculators and different data formats (whether it
> be lat/long fields, geohashes, or something else in the future).
> Patch to be added soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
