Hi,
I guess it's useful in some edge cases where the user wants to search
different entities with one query. As long as everything is in the same index
scoring is a lot easier (I don't know if it even works otherwise). I guess
that could be done by indexing a common supertype, but sometimes that's not possible.
I don't get the filtering out part though. Doesn't the query API take care of
that?
If not, I think it should definitely be doing that (query for the actual class).
cheers,
Martin Braun
martinbraun123(a)aol.com
www.github.com/s4ke
-----Original Message-----
From: Gunnar Morling <gunnar(a)hibernate.org>
To: hibernate-dev <hibernate-dev(a)lists.jboss.org>
Sent: Wed, Aug 12, 2015 4:30 pm
Subject: [hibernate-dev] [HSEARCH] Usefulness of index sharing
Hibernate Search aficionados,
I am wondering what that's the rationale for
offering the feature of
index sharing [1].
The ref guide says "there is
really not much benefit in sharing
indexes". It complicates queries, as an
additional filter on the type
field must be applied in case of targeting only
one entity using a
shared index.
Should we consider to drop this feature in
HS 6?
Thanks,
--Gunnar
[1]
https://docs.jboss.org/hibernate/search/5.4/reference/en-US/html_single/#...
_______________________________________________
hibernate-dev
mailing
list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev