elasticsearch - Is the order of operations guaranteed in a bulk update? -


i sending delete , index requests elasticsearch in bulk (the example adapted from docs):

{ "delete" : { "_index" : "test", "_type" : "type1", "_id" : "1" } } { "index" : { "_index" : "test", "_type" : "type1", "_id" : "1" } } { "field1" : "value1" } 

the sequence above intended first delete possible document _id=1, index new document same _id=1.

is order of actions guaranteed? in other words, example above, can sure delete not touch document indexed afterwards (because order not respected reason or another)?

the delete operation useless in scenario, if index document same id, automatically , implicitly delete/replace previous document same id.

so if document id=1 exists, sending below command replace (read delete , re-index it)

{ "index" : { "_index" : "test", "_type" : "type1", "_id" : "1" } } { "field1" : "value1" } 

Comments

Popular posts from this blog

java - Jasper subreport showing only one entry from the JSON data source when embedded in the Title band -

serialization - Convert Any type in scala to Array[Byte] and back -

SonarQube Plugin for Jenkins does not find SonarQube Scanner executable -