There’s no restriction on the <unkqueKey> except in the sense that if you add a document with the _same_ <uniqueKey> as a document already in the index, Solr will delete the old document and add a new one. That would account for your deleted documents.
> On Mar 4, 2019, at 8:31 AM, Juergen Melzer (DPDHL IT Services) > <juergen.mel...@dpdhl.com.INVALID> wrote: > > No, we are using only > org.apache.solr.client.solrj.SolrClient#addBeans(java.util.Collection<?>) > and we have an autocommit used. > > > Gruß > Jürgen Melzer > > -----Ursprüngliche Nachricht----- > Von: Walter Underwood [mailto:wun...@wunderwood.org] > Gesendet: Montag, 4. März 2019 17:29 > An: solr-user@lucene.apache.org > Betreff: Re: Full index xreation is deleting documents > > Do you update documents? That deletes the old and adds the new. > > wunder > Walter Underwood > wun...@wunderwood.org > http://observer.wunderwood.org/ (my blog) > >> On Mar 4, 2019, at 8:27 AM, Juergen Melzer (DPDHL IT Services) >> <juergen.mel...@dpdhl.com.INVALID> wrote: >> >> Hi all >> >> We have a strange situation. When we are creating the index we see a lot of >> documents that are marked as deleted. But we don't delete any document while >> we are adding documents. >> We are thinking about the uniquekey that might be that problem. Is there any >> restriction regarding using a unique long value as the id? >> >> >> Regards >> Juergen >> >
