I observed a version mis match when I run a deleteByQuery and when do a
bulk delete by Id.
So If I have a doc I want to search and delete it I have two option either
use
deleteByQuery
Search the document and issue a bulk delete
these both delete the documents ----
But when I index the document with same Id which was deleted
deleteByQuery starts the indexing with version 1
where other (Search the document and issue a bulk delete) starts the
indexing with lastVersion+1.
Note that after 60s by default, whatever the method you used, version number will restart from 1.
Are you sure you did not hit this?
Is it something you can reproduce with a script?
Note that you can control this period using settings.gc_deletes at index level.
Le 20 décembre 2013 at 09:37:23, Arjit Gupta (arjit292@gmail.com) a écrit:
Hi,
I observed a version mis match when I run a deleteByQuery and when do a bulk delete by Id.
So If I have a doc I want to search and delete it I have two option either use
deleteByQuery
Search the document and issue a bulk delete
these both delete the documents ----
But when I index the document with same Id which was deleted
deleteByQuery starts the indexing with version 1
where other (Search the document and issue a bulk delete) starts the indexing with lastVersion+1.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.