Hi Matthias, I found some scenario where could be tricky having different names for the unique key.
1) Inter collection search - In this case more than callign the uniqueKey "Id" or not, is the fact of using the same uniqueKey across all the collections. If not when you aggregate the results, Solr will fail to recognize the unique keys which are different from the aggregator uniqueKey ( and this will result in losing the results coming from the collection which uses a different uniqueKey) 2) In the elevation component config you identify the doc to boost specifying the Id e.g. <elevate> <query text="AAA"> <doc id="A" /> ... The "id" label is slightly incorrect, as it should be : <doc uniqueKey="A" /> Indeed you don't need to define an "id" field in your document to work with the elevation component as in the code Solr will fetch the uniqueKey field from the schema ( schema.getUniqueKeyField()) . But it may sound a little bit confusing for a new user which decided to use a different uniqueKey field. These two are the first considerations that came up to my mind, the second is more to clarify the syntax of the config file, as you are not going to have any problem with the uniqueKey field name. If anything else pop out I will let you know! Cheers ----- --------------- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- View this message in context: http://lucene.472066.n3.nabble.com/Issues-with-uniqueKey-id-tp4318662p4318944.html Sent from the Solr - User mailing list archive at Nabble.com.
