Very good note, I missed that. I need the development environment in front
of me to remember all the different class names correctly. ;-)
-- j
On 3/1/06, Doug Cutting <[EMAIL PROTECTED]> wrote:
>
> Jeff Rodenburg wrote:
> > Following on the Range Query approach, how is performance? I found th
Jeff Rodenburg wrote:
Following on the Range Query approach, how is performance? I found the
range approach (albeit with the exact values) to be slower than the
parsed-string approach I posited.
Note that Hoss suggested RangeFilter, not RangeQuery. Or perhaps
ConstantScoreRangeQuery, which i
Thanks to everyone on the replies. I'm going to try several of these
approaches and with equivalent data sets and run some side-by-side tests.
No timeframes guarantees here, but I'll report back with the different
approaches and the test results.
cheers,
-- j
On 2/28/06, Chris Hostetter <[EMAI
: Very good points, I hadn't considered the term frequency of the digits
: affecting scoring. As an aside, can that aspect of the score be ignored for
: these fields?
The easiest way is to use a boost that is so low it's insignificant, or
you could subclass TermQuery and override getSimilarity t
Very good points, I hadn't considered the term frequency of the digits
affecting scoring. As an aside, can that aspect of the score be ignored for
these fields?
I need to spend more time with FunctionQuery, I haven't given it the
attention it deserves.
Great feedback, thanks for the notes.
-- j
Michael -
Great thoughts, and thanks for the feedback.
Following on the Range Query approach, how is performance? I found the
range approach (albeit with the exact values) to be slower than the
parsed-string approach I posited.
On the custom scoring, is the distance element for sorting or as a
ssage-
> From: John Powers [mailto:[EMAIL PROTECTED]
> Sent: Tue 2/28/06 3:53 PM
> To: java-user@lucene.apache.org
> Cc:
> Subject: RE: Hacking proximity search: looking for feedback
>
> I don't know if this matters, but we do all of our geolocating in sql
&
[mailto:[EMAIL PROTECTED]
Sent: Tue 2/28/06 3:53 PM
To: java-user@lucene.apache.org
Cc:
Subject:RE: Hacking proximity search: looking for feedback
I don't know if this matters, but we do all of our geolocating in sql
with decent speed. All the trig is in the query itsel
ility?
-Original Message-
From: Bryzek.Michael [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 2:49 PM
To: java-user@lucene.apache.org
Subject: RE: Hacking proximity search: looking for feedback
Jeff -
This is an interesting approach. On our end, we have experimented with
two var
Jeff -
This is an interesting approach. On our end, we have experimented with
two variants:
Variant 1: Use Range Query
Rather than precomputing the boolean clauses yourself, index encoded
latitude and longitude values and use a Range Query. We encode by
adding 1000 to each of the values. Note: W
: Geo definition:
: Boxing around a center point. It's not critical to do a radius search with
: a given circle. A boxed approach allows for taller or wider frames of
: reference, which are applicable for our use.
if you are just loking to confine your results to a box then i think
RangeFilteri
11 matches
Mail list logo
