[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=45919#comment-45919 ] 

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

@David Perhaps we should resolve this and I will create a second Jira item for the other issue? Or should we keep this open here?
Just to summarize: the behaviour is that if SubItem is indexed from the root, the SubItem index itself will only contain those fields that were specified in the root of Item. However, SubItem itself as a *root item* may have a different path configuration and require different fields. I'm not sure if this should be considered a bug or not since the whole point is to avoid unnecessary index paths. So, probably not. In any case, the result is that the SubItem index itself will only be guaranteed to be in a correct state if you save the relevant SubItems directly or MassIndex it.

> 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