[
https://hibernate.onjira.com/browse/HSEARCH-1049?page=com.atlassian.jira....
]
Sanne Grinovero commented on HSEARCH-1049:
------------------------------------------
I agree this should be solved regardless.
Adding an explicit Field might work, but I'm not sure what would happen if we end up
including it twice in the index, that should be tested carefully.
We can hardly check against including the id field multiple times - in fact bridges are
free to do so, as there might be valid use cases.
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
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