[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-1049) includePaths bombs on inclusion of id members
[
https://hibernate.onjira.com/browse/HSEARCH-1049?page=com.atlassian.jira....
]
Sanne Grinovero commented on HSEARCH-1049:
------------------------------------------
Yes I agree with your expectations, but since "includePaths" is relatively
young, I'm not sure how many tests cover for this, we should improve on that side and
you're welcome to add some. That's the only way I know to answer you "that
works".
If we're speaking about the API intentions: includePaths is an extension to
@IndexedEmbedded, so yes it definitely defines which fields are included and which are
not, but as it was with the "depth" strategy or any older @IndexedEmbedded, to
have its fields updated by a change in one of the entities affecting the indexed path, you
would need @ContainedIn to trigger the update, walking the path backwards.
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
Assignee: Davide D'Alto
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