Hi Emmanuel, no doubts that you knew about this, but users don't
expect it (and even Hardy forgot it :-P ).
I thought to bring it up here just to ping your brains, so that in
background while thinking at more urgent stuff one day somebody will
I guess we could store enough information in the index using payloads,
(storing a sequential id of the relation) but don't know about
implementing appropriate filtering; also payloads would work only for
"one level" relations, not deeper graphs. I'm just trying to throw
some ideas on the table
Would be cool if we could find a solution on this.
2010/1/19 Emmanuel Bernard <emmanuel(a)hibernate.org>:
Your use case works (with a class level bridge).
Another one is to reverse the query
author.firstname=Sue AND author.lastname=Smith
and then do
Have you read Hibernate Search in Action ;P
On 18 janv. 2010, at 21:04, Sanne Grinovero wrote:
> there's a limitation in Hibernate Search's capabilities of mapping
> structured objects,
> there's a good explanation of this problem here:
> This is something I'm aware of since my first use of Search, I was
> assuming you know about it?
> I couldn't think of a good solution so far, besides the awful
> workaround I suggested in the forums.
> Better ideas?
> hibernate-dev mailing list