Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: patrick o'leary [mailto:pj...@pjaol.com]
> > Sent: Monday, April 20, 2009 3:33 AM
> > To: java-user@lucene.apach
; From: patrick o'leary [mailto:pj...@pjaol.com]
> Sent: Monday, April 20, 2009 3:33 AM
> To: java-user@lucene.apache.org
> Subject: Re: LocalLucene/Lucene Spatial
>
> 1) The only reason for ConstantScoreQuery is because it lets me convert
> the
> LocalLucene filter to a query
1) The only reason for ConstantScoreQuery is because it lets me convert the
LocalLucene filter to a query.
2) TierRangeQuery- not at the moment, we're not really doing a range search,
we're pulling predefined id's (e.g. a shape) from the index using the term
enumerator.
Average time take for a bo
Is there a reason the Query build is from a bitset via a ConstantScoreQuery
instead a RangeQuery? Seems we would be paying a penalty for loading the
bitset, esp the bitset would be rather sparse.
Furthermore, is TrieRangeQuery planning to be somehow used in the spatial
package?
Thanks
-John
On
In the trunk, see contrib/spatial. I believe it is all committed and
being worked on by interested contributors: http://svn.apache.org/repos/asf/lucene/java/trunk/contrib/spatial/
-Grant
On Mar 18, 2009, at 12:05 PM, Jamie Johnson wrote:
I am working on a project that is already using Lucene
