parent
9acd2fd1fd
commit
ec335c7c34
|
@ -137,7 +137,7 @@ $ curl -s -H "Content-Type: application/x-ndjson" -XPOST localhost:9200/_bulk --
|
|||
|
||||
[discrete]
|
||||
[[bulk-optimistic-concurrency-control]]
|
||||
===== Optimistic Concurrency Control
|
||||
===== Optimistic concurrency control
|
||||
|
||||
Each `index` and `delete` action within a bulk API call may include the
|
||||
`if_seq_no` and `if_primary_term` parameters in their respective action
|
||||
|
@ -168,7 +168,7 @@ appropriate backing index for the stream.
|
|||
|
||||
[discrete]
|
||||
[[bulk-wait-for-active-shards]]
|
||||
===== Wait For Active Shards
|
||||
===== Wait for active shards
|
||||
|
||||
When making bulk calls, you can set the `wait_for_active_shards`
|
||||
parameter to require a minimum number of shard copies to be active
|
||||
|
|
|
@ -162,7 +162,7 @@ PUT /test
|
|||
--------------------------------------------------
|
||||
|
||||
[[create-index-wait-for-active-shards]]
|
||||
===== Wait For active shards
|
||||
===== Wait for active shards
|
||||
|
||||
By default, index creation will only return a response to the client when the primary copies of
|
||||
each shard have been started, or the request times out. The index creation response will indicate
|
||||
|
|
|
@ -66,7 +66,7 @@ and then the previous write index can be closed.
|
|||
// end::closed-index[]
|
||||
|
||||
[[open-index-api-wait-for-active-shards]]
|
||||
===== Wait For active shards
|
||||
===== Wait for active shards
|
||||
|
||||
// tag::wait-for-active-shards[]
|
||||
|
||||
|
|
Loading…
Reference in New Issue