Hi,
I am not quite sure I follow. Why fieldname? And do you mean Lucene
Document field name or
a entity field name?
I think originally we discussed defineBoost(String fieldName, Object
value), but decided that
the fieldName parameter was not needed.
You can place the @DynamicBoost annotation on class or field level. On
class level you define a
dynamic boost for the whole entity and on field level just for this field.
Do you want to be able
to place a @DynamicBoost on class level and call for each indexed field
defineBoost(String fieldName, Object value),
where fieldName would be the current index field name and value the
indexed entity?
One thing we have not done though is to add @DynamicBoost to @Field. Right
now you can only
specify @DynamicBoost directly on a field and the dynamic boost will apply
to all @Field annotations defined
on this field.
--Hardy
On Fri, 04 Dec 2009 09:44:30 -0300, Emmanuel Bernard
<emman...@hibernate.org> wrote:
> I think the BoostStrategy interface is not right.
> You can't adjust the boost strategy according to the field name and I
> think that's important (assuming dynamic boosting is used).
>
> We probably should rework it to do
>
> interface BoostStrategy {
> void defineBoost(String fieldName, Object value);
> }
>
> WDYT?
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
