[
https://hibernate.onjira.com/browse/HSEARCH-1049?page=com.atlassian.jira....
]
Davide D'Alto commented on HSEARCH-1049:
----------------------------------------
Sorry I pressed enter too soon...
There is a problems in this case:
Because you have specified includePaths in Subitem the depth is set to 0 and therefore the
relatedItems are not indexed (they are indexed when creating the index for SubItem under
item.id).
subitem.item.id is going to be created if you specified it in Item with:
{code}
@IndexedEmbedded(prefix="subitem.", includePaths={"id",
"item.id"})
{code}
Another problem is that HibernateSearch is actually loading all the JPA classes when
indexing and not only the one annotated with @Indexed (is this correct Sanne?), because of
this something goes wrong in the validation of the paths. I think we should disable it in
the class: DocumentBuilderContainedEntity.java
I'm not sure if I have been clear but it's a quite complicated part.
includePaths bombs on inclusion of id members
---------------------------------------------
Key: HSEARCH-1049
URL:
https://hibernate.onjira.com/browse/HSEARCH-1049
Project: Hibernate Search
Issue Type: Bug
Components: engine
Affects Versions: 4.1.0.Beta2
Reporter: Marc Schipperheyn
Priority: Blocker
Fix For: 4.1.0.Final
When I include id members on includePaths, I get
Found invalid @IndexedEmbedded->paths configured on class nl.project.model.Item,
member subitem: item.id
I use ids a lot and in many cases they are all I'm interested in.
E.g.
@IndexedEmbedded(prefix="location.",includePaths={"city.id","city.city","country.id","city.region.id"})
public Address getAddress() {
return address;
}
will indicate all id fields as erronous.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira