If you went with the FunctionQuery approach for sorting by distance, would
there be any way to use the output of the FunctionQuery to limit the
documents to those within a certain radius? Or is it just for boosting
documents, not for filtering?
Also, even if you're just using it for boosting, is
Don't know if you ever found a fix for this issue, but I saw experienced it
tonight while trying to run solr through jetty in eclipse. The custom
RequestHandler plugin was loading fine when running jetty normally from the
command-line, but running it through eclipse hit the ClassCastException.
I
talking about the demo ui, it's a little piece of html & JS, you
> can pull directly from the jar.
> I've not included that in the repository.
>
> HTH
> P
>
> Doug Daniels wrote:
>> Hi Patrick,
>>
>> Are the solr components of that demo in the reposi
Hi Patrick,
Are the solr components of that demo in the repository as well? I couldn't
find them there.
Best,
Doug
patrick o'leary wrote:
>
> As far as I'm concerned nothings going to beat PG's GIS calculations,
> but it's tsearch was
> a lot slower than myisam.
>
> My goal was a single sol
Hi,
I'm trying to find a way to express a certain query and wondering if
anyone could help.
The query is against a schema that stores the user_ids who have worked
on each document in a multi-value integer field called 'user_ids'. I'd
like to query solr for all documents that anyone other th
Nevermind! I figured out that the qf parameter handles any field names
that match a dynamic field name pattern, regardless of whether a field
is defined with that name.
-Doug
Doug Daniels wrote:
Hi,
I noticed that the "field list" (fl) parameter ignores field names that
it can
Hi,
I noticed that the "field list" (fl) parameter ignores field names that
it cannot locate, while the "query fields" (qf) parameter throws an
exception when fields cannot be located. Is there any way to override
this behavior and have qf also ignore fields it cannot find?
This would be pr
