Hi

I have 2 classes Contact and Address. The following shows snippets of code for both classes:
Contact.java


Address.java


I have some code to perform searching on Address



Using the following fields:


I'm not sure if this is a problem or perhaps i am doing it incorrectly. When i ran my test case using the above snippets of code i was not getting any results (for example i was trying to search on address1). I have set up Contact according to the documentation. However when i looked at sample test cases (hibernate search distribution) i noticed collections had @IndexEmbedded instead of @ContainedIn. So i updtaed my code to the following:



And then when I ran my test case it worked. I was wondering if someone could tell me whether i use just @IndexEmbedded or @ContainedIn for querying collections. Obviously @IndexEmbedded worked but I am not sure if this is the correct approach. Any help would be appreciated.

Hi

Any chance if someone might be able to help on this matter....


Thanks

@IndexedEmbedded on addresses of Contact means that you will be able to do queries like addressed.address1

@IndexedEmbedded on contact of Address means that you will be able to do queries like contact.name

@ContainedIn is here to say, if you update the object having a @ContainedIn, you need to update the index data of the associated object
So typically @ContainedIn is on the other side of an @indexedEmbedded

Hi there


Thanks for your reply. So basically i need to have both.

but not in the same property

Hmm...sorry i'm slightly confused. If i need to do queries such as addresses.address1 = something then i need @IndexEmbedded on addresses in Contact. But I presume I need @ContainedIn as well on addresses based on the description:

"@ContainedIn is useful on embedded objects that are also entities (like Address in this example): it basically means that when an address entity is updated, the index document of the associated Place(s), also has to be updated."


Thanks

no you need @ContainedIn on the other side of the relationship

Ok. So I need to do the following:



and on the Address side do the following:



This means that when Address is updated then the index on Contact needs to be updated as well because it contains a set of address entities (sorry talking out aloud then!)

yes you're correct, except that you forgot the mappedBy attribute in @OneToMany to make it a true bidirectional relationship (your current example has 2 unidirectional relationships)

ok..so final result should look like this

Contact.java


Address.java



Thanks again

yes, targetEntity is not useful though