Hi Gunnar,
I'm using a single generic entity to represent multiple domain entities
in the context of a single SearchFactory. So it seems we fall into the
more complex case of "more abstract representation of types than class
objects". Is this still doable in hsearch? I'm keeping my fingers
cro
2013/9/9 Adrian Nistor
> Hi Gunnar,
>
> I currently use a single generic indexed entity which represents the
> multitude of protobuf defined domain types. This approach is not
> necessarily ideal but was forced to adopt it because of the way hsearch
> currently works. Other projects do the same
Hi Adrian,
We have been contemplating some ideas around your requirements. Are you
working with several "types" (as defined by ProtoBuf files) or only one
such type per one of your caches (and thus afaics SearchFactory)?
In case of the latter, one idea would be that you always target your
generic
Adrian found a few problematic limitations in Hibernate Search during
its integration of the HQL query parser and the Hibernate Search back
end.
Composite bridge::
https://hibernate.atlassian.net/browse/HSEARCH-1397
Injection of services into a FieldBridge::
https://hibernate.atlassian.net/browse
