lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Earwin Burrfoot <>
Subject Re: Proposal: Scorer api change
Date Wed, 09 Jun 2010 11:24:36 GMT
> Can we represent the Query
> state in some general structure, that no matter which Query you get, you'll
> know how to score it?

No. You could go for unified interface that allows you to express
different query states, like a set of untyped key-values, but you'll
end up switching on these keyvalues in the end.

It's better to define a set of matchers, and then produce visitors
that compute scores. These visitors are then free to specialize on
matchers or not, or ignore the whole tree completely.

Kirill Zakharenko/Кирилл Захаренко (
Phone: +7 (495) 683-567-4
ICQ: 104465785

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message