Hello If the insert/delete are done with two different threads (and with no synchronization), it could be possible that the new records are getting deleted. We might have to dig a bit into Solr code I guess.
Deepak "The greatness of a nation can be judged by the way its animals are treated - Mahatma Gandhi" +91 73500 12833 [email protected] Facebook: https://www.facebook.com/deicool LinkedIn: www.linkedin.com/in/deicool "Plant a Tree, Go Green" Make In India : http://www.makeinindia.com/home On Wed, Oct 13, 2021 at 3:16 PM Saur, Alexandre (ELS-AMS) < [email protected]> wrote: > Hi, > > I have a (noobie) question about Solr 8 autocommit behaviour. This is my > scenario: > > - Autocommit configured in solrconfig > - ETL job that indexes thousands of documents whenever it runs > > The ETL job updates the collection in the following manner: first it > deletes a series of documents based on a key and then it adds new ones > using the same key, with updated values (the transactions are always in > this order). The job (client) does not commit its transactions (neither > delete nor insert). > > Given this scenario, is it possible that the delete/insert order is played > differently when Solr autocommits? In other words, is it possible that the > insert gets deleted? > > > > > ________________________________ > > Elsevier B.V. Registered Office: Radarweg 29, 1043 NX Amsterdam, The > Netherlands, Registration No. 33158992, Registered in The Netherlands. >
