Re: [hibernate-dev] adding a binding to a boolean method in Search's @Field to enable/disable
Hi Emmanuel,
it's not my usecase, it's described in the forums:
https://forum.hibernate.org/viewtopic.php?f=9&t=1002800
You mean something like this:
boolean isFieldEnabled(Object value, Object entity, String field);
(having value,entity,field parameters as in Discriminator )?
Sanne
2010/2/22 Emmanuel Bernard <emmanuel(a)hibernate.org>:
I guess we can do like we've done for @AnalyzerDiscriminator.
But can you describe your use case a bit deeper?
On 22 févr. 2010, at 09:29, Sanne Grinovero wrote:
> Hello all,
> there's a user on Search's forum which is asking for a new feature:
>
> https://forum.hibernate.org/viewtopic.php?f=9&t=1002800
>
> We already had cases of people wanting to enable/disable indexing at
> instance level; in this case he wants to avoid indexing certain fields
> in some conditions; reading a boolean property in the same indexed
> instance would be good enough.
> I'm unsure about the binding expression, but the idea of having each
> Field enabled/disabled independently would indeed have helped me in
> other situations, preventing me from writing a full ClassBridge for
> just some special fields.
>
> Regards,
> Sanne
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev