[
https://issues.apache.org/jira/browse/LUCENE-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965295#action_12965295
]
Simon Willnauer commented on LUCENE-2139:
-----------------------------------------
bq. 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.
I was actually hoping somebody says that before I write to the list and get my
head cut off :) I think that is the best idea. we should nuke the spatial
contrib entirely and start from zero in the modules area. IMO we should move
all existing stuff from solr into there and let glue code reside under solr.
I hope I have time to write that up and propose it on the list.
simon
> 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]
