[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-1049) includePaths bombs on inclusion of id members

[Marc Schipperheyn (JIRA)]

    [ https://hibernate.onjira.com/browse/HSEARCH-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46037#comment-46037 ] 

Marc Schipperheyn commented on HSEARCH-1049:
--------------------------------------------

@Sanne I wasn't aware that it was triggered by containedIn, I always thought it was triggered by IndexedEmbedded. But I'm not sure if it matters. If you use includePaths, the object is to avoid indexing unnecessary fields. So, the embedded index (SubItem), when created through a save of the embedding entity (Item) will only have the included paths, right? If you don't save SubItem separately, it wouldn't have the "extra" fields, right? I'm saying "right" not to be pedantic but rather to confirm. So, I can imagine people not realizing this. Hence the suggestion. Perhaps I'm wrong.

> 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