What's your use case?
I am not against that feature but I don't think it covers all use cases:
- I want a higher boost for more recent documents
- I change priority in my categories depending on the marketing mood
Said otherwise, can have a true dynamic boost defined at query time,
not at indexing time.
I think Solr has something named FunctionQuery that can do that.
On Apr 29, 2009, at 16:47, Sanne Grinovero wrote:
I'm currently needing to be able to define a per-entity INSTANCE
different Boost, not just the type.
Currently I could obtain this functionality by using a custom
classbridge, but the entity is quite complex and building my own
classbridge I will have to map all fields myself loosing the
flexibility of annotations for the current type and
I'd like to add a new parameter to @Boost; currently it has a float
I'd like to add a new parameter:
where BoostScorer is an interface having something like
public float score(Object value);
The annotation would default to an implementation returning constant
This would have an interaction with the existing "value" parameter:
IMHO they should
multiply each other, so I'd change the existing value to also have a
default of 1.0f
and people might want to change one or both values.
Setting both values might be useful to reuse the same impl on
and still be able to statically scale the result from the
score(Object) function, without having to
rewrite a new implementation.
What do you think?
hibernate-dev mailing list