Hi, I would not use ID (uniqueKey) as signature field, query elevation would never work properly with such a set up, change a document's content, and it 'll get a new ID.
If i remember correctly this factory still deletes duplicates if signatureField is not uniqueKey. Regarding SOLR-3473, nobody seems to be working on that. Regards, Markus -----Original message----- > From:Ronja Koistinen <ronja.koisti...@helsinki.fi> > Sent: Monday 5th March 2018 15:32 > To: email@example.com > Subject: Solr Cloud: query elevation + deduplication? > > Hello, > > I am running Solr Cloud 6.6.2 and trying to get query elevation and > deduplication (with SignatureUpdateProcessor) working at the same time. > > The documentation for deduplication > (https://lucene.apache.org/solr/guide/6_6/de-duplication.html) does not > specify if the signatureField needs to be the uniqueKey field configured > in my schema.xml. Currently I have my uniqueKey set to the field > containing the url of my documents. > > The query elevation seems to reference documents by the uniqueKey in the > "id" attributes listed in elevate.xml, so having the uniqueKey be the > url would be beneficial to my process of maintaining the query elevation > list. > > Also, what is the status of this issue I found? > https://issues.apache.org/jira/browse/SOLR-3473 > > -- > Ronja Koistinen > University of Helsinki > >