]
j nadler commented on HSEARCH-528:
----------------------------------
For what it's worth: I changed my app to index all the subtypes of Parent. This
makes MassIndexer work. I changed all my queries to exclude (MUST_NOT) the subclass that
I didn't want indexed. I pay a small price in that the indexes are a bit larger than
they need to be, but its not a major issue. I still think this should work differently,
but you can downgrade the priority IMHO.
MassIndexer attempts to index non-indexed subclasses of indexed
types
---------------------------------------------------------------------
Key: HSEARCH-528
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-528
Project: Hibernate Search
Issue Type: Bug
Affects Versions: 3.2.0.Beta1, 3.2.0.CR1, 3.2.0.Final
Reporter: Sanne Grinovero
Fix For: 3.3.0
quoting comments from HSEARCH-526:
j nadler :
{quote}Sanne,
I have @Indexed class Parent, @Indexed class Child1 extends Parent, @Indexed class Child2
extends Parent, unindexed class Child3 extends Parent.
I create an indexer fullTextEntityManager.createIndexer(Parent.class), it seems that it
then fetches all Parent entities. This includes all Child3 entities but Child3 is not
indexed. It seems like the MassIndexer attempts to index them anyway.
Best behavior might be to ignore these (explicitly check if the concrete subtype is
@Indexed, skip that record if not, possibly log a warning) or as you say it could at least
throw an error that makes it clear what the developer (me) did wrong.
Thanks!
{quote}
Emmanuel Bernard :
{quote}Ah, right. Sanne, you should use the same algorithm we use in the query building
process to check the list of indexed subclasses to create the list of indexes to
merge.{quote}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: