[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....
]
Marc Schipperheyn commented on HSEARCH-1049:
--------------------------------------------
Ok, well, had a look. The reason that the id field member is not included in the
"approved paths" seems to be that only fields are bound that have a Field
annotation. As I'm not so familiar with the code, judging by the checkForField method,
I would conclude that only Field annotated fields are eligible as includePaths. So, I
tried adding a class bridge created field to an includePaths and sure enough, it bombed
also.
I'm not sure what the consequences are of binding a Field, but otherwise I would
suggest that idFields should be "bound" also. Class level generated fields can
probably be tied in to whatever mechanism makes sure we can search on them now.
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