I am not sure @DocumentId is the right place to host it. Should it be rather on
the embedding entity to be able to customize in which scenario id is indexed?
In a way, includePath="city.id" is the indicator I am looking for.
On 16 févr. 2012, at 11:54, Sanne Grinovero wrote:
> This is related t
This is related to HSEARCH-1049: it seems that the new includePaths
feature is not accepting paths including the id of embedded objects,
as in:
@IndexedEmbedded(prefix="location.",includePaths={"city.id","city.city","country.id","city.region.id"})
public Address getAddress() { return address; }
A
