> In the near future, you can do a real query-time boost (score multiplication)
> by another field or function
> https://issues.apache.org/jira/browse/SOLR-334
>
> And even quickly update all the values of the field being used as the boost:
> https://issues.apache.org/jira/browse/SOLR-351
Thanks,
On 10/5/07, Mike Klaas <[EMAIL PROTECTED]> wrote:
> The other option is to use a function query on the value stored in a
> field (which could represent a range of 'badness'). This can be used
> directly in the dismax handler using the bf (boost function) query
> parameter.
In the near future, you
On 5-Oct-07, at 3:01 PM, Kyle Banerjee wrote:
If you know at index time that the document is shady, the easiest way
to de-emphasize it globally is to set the document boost to some
value other than one.
...
I considered that, but assumed we'd get the values wrong at first and
have to do a lot
> If you know at index time that the document is shady, the easiest way
> to de-emphasize it globally is to set the document boost to some
> value other than one.
>
> ...
I considered that, but assumed we'd get the values wrong at first and
have to do a lot of tinkering before we got it right. Is
On 5-Oct-07, at 2:06 PM, Kyle Banerjee wrote:
Howdy all,
We are attempting to provide access to about 8 million records of
highly variable quality and length. In a nutshell, we are trying to
find a way to deprioritize "suspect" records without discriminating
against useful records that happen t
