lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Helleringer (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-2139) Cleanup and Improvement of Spatial Contrib
Date Wed, 01 Dec 2010 08:59:11 GMT

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

Nicolas Helleringer commented on LUCENE-2139:
---------------------------------------------

bq. Yep - but they are normally tri-range (i.e. Lucene Numeric) ranges, so pretty efficient
anyway.
bq. 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).
>From personnal experience I do not aggre as I deployed lucene tier spatial to solve performance
issue with a double range query on two fields
But that is not factual : i do aggree with Chris that the better is to work on benchmarking
to 'prove' this and movve forward.

bq. @deprecate the contrib in 3x, nuke in 4x
Pity to remove code before replacing one is still not here : what will the users do ?

The more important thus is to move forward : I will be pleased to help on trying to port tier
support if anybody is interessed in it to the new section where spatial lives

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message