No, there's not a way to control Similarity on a per-request basis.
Some factors from Similarity are computed at index-time though.
What factors are you trying to tweak that way and why? Maybe doing boosting
using some other mechanism (boosting functions, boosting clauses) would be a
better way to go?
Erik
On Jun 16, 2011, at 14:55 , Gabriele Kahlout wrote:
> Hello,
>
> I'm testing out different Similarity implementations, and to do that I
> restart Solr each time I want to try a different similarity class I change
> the class attributed of the similiary element in schema.xml. Beside running
> multiple-cores, each with its own schema, is there a way to tell the
> RequestHandler which similarity class to use?
>
> --
> Regards,
> K. Gabriele
>
> --- unchanged since 20/9/10 ---
> P.S. If the subject contains "[LON]" or the addressee acknowledges the
> receipt within 48 hours then I don't resend the email.
> subject(this) ∈ L(LON*) ∨ ∃x. (x ∈ MyInbox ∧ Acknowledges(x, this) ∧ time(x)
> < Now + 48h) ⇒ ¬resend(I, this).
>
> If an email is sent by a sender that is not a trusted contact or the email
> does not contain a valid code then the email is not received. A valid code
> starts with a hyphen and ends with "X".
> ∀x. x ∈ MyInbox ⇒ from(x) ∈ MySafeSenderList ∨ (∃y. y ∈ subject(x) ∧ y ∈
> L(-[a-z]+[0-9]X)).
