: essentially, this is:
: +north:[* TO nnn] +south:[sss TO *] +east:[* TO eee] +west:[www TO *]
: Would this be better as four individual filters?
it depends on the granularity you exepct clients to query with ... if
cleents can get really granular, then the odds of reuse are lower, so the
ad
Lance Norskog wrote:
Is it not possible to make a grid of your boxes? It seems like this would be
a more efficient query:
grid:N100_S50_E250_W412
This is how GIS systems work, right?
something like that... I was just checking if I could get away with
range queries for now... I'll also
: solr-user@lucene.apache.org
Subject: Re: range vs. filter queries
>>
>> Would this be better as four individual filters?
>
> Only if there were likely to occur again in combination with different
> constraints.
> My guess would be no.
this is because the filter could
On Feb 11, 2008 9:13 PM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> >>
> >> Would this be better as four individual filters?
> >
> > Only if there were likely to occur again in combination with different
> > constraints.
> > My guess would be no.
>
> this is because the filter could not be cached?
Would this be better as four individual filters?
Only if there were likely to occur again in combination with different
constraints.
My guess would be no.
this is because the filter could not be cached?
Since i know it should not cached, is there any way to make sure it does
not purge usefu
On Feb 11, 2008 8:51 PM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> Hello-
>
> I'm working on a SearchComponent that should limit results to entries
> within a geographic range. I would love some feedback to make sure I'm
> not building silly queries and/or can change them to be better. I have
>
Hello-
I'm working on a SearchComponent that should limit results to entries
within a geographic range. I would love some feedback to make sure I'm
not building silly queries and/or can change them to be better. I have
four fields:
The component looks for a "bounds" argument a
