[ 
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965161#action_12965161
 ] 

Chris Male commented on LUCENE-2139:
------------------------------------

I think the overall direction of Spatial Lucene has changed considerably since 
this work was done.  There have been considerable issues found with the 
Cartesian Tier code which this patch doesnt address.  Equally, issues of 
stateful Filters has brought to attention that the SpatialFilter breaks alot of 
Filter principals.

I say we close these issues and begin moving what code we feel is salvagable to 
a spatial module where we can work closely with the Solr code.

> 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]

Reply via email to