Thanks
s.grinovero wrote:
you can specify that they should both use the same field, but I'd really discourage this.
Once they are indexed this way, you're stuck and can't separate them if you need (for example, to apply some boosting).
Much better, have your queries written in such a way that they look into both fields.
I see your point, but still don't know how to annotate the classes so I can search both fields. If it's just adding the FieldBridge mentioned below, could you please supply an example that would work? Thanks again.
s.grinovero wrote:
As a sidenode, make sure you define a FieldBridge on alternateNames: @ElementCollection is not automatically supported right now.