> 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/Кирилл Захаренко (ear...@gmail.com) Phone: +7 (495) 683-567-4 ICQ: 104465785 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
