anchor.diff:  // TESTRESPONSE[s/"_seq_no" : 3/"_seq_no" : $body.items.3.update._seq_no/]
   // TESTRESPONSE[s/"_primary_term" : 4/"_primary_term" : $body.items.3.update._primary_term/]
   
  -The endpoints are `/_bulk` and `/{index}/_bulk`. When the index is provided, it
  -will be used by default on bulk items that don't provide it explicitly.
  -
  -A note on the format. The idea here is to make processing of this as
  -fast as possible. As some of the actions will be redirected to other
  -shards on other nodes, only `action_meta_data` is parsed on the
  -receiving node side.
  -
  -Client libraries using this protocol should try and strive to do
  -something similar on the client side, and reduce buffering as much as
  -possible.
  -
  -The response to a bulk action is a large JSON structure with the individual
  -results of each action that was performed in the same order as the actions that
  -appeared in the request. The failure of a single action does not affect the
  -remaining actions.
  -
  -There is no "correct" number of actions to perform in a single bulk
  -call. You should experiment with different settings to find the optimum
  -size for your particular workload.
  -
  -If using the HTTP API, make sure that the client does not send HTTP
  -chunks, as this will slow things down.
  -
  -[float]
  -[[bulk-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
  -and meta data lines. The `if_seq_no` and `if_primary_term` parameters control
  -how operations are executed, based on the last modification to existing
  -documents. See <<optimistic-concurrency-control>> for more details.
  -
  -
  -[float]
  -[[bulk-versioning]]
  -==== Versioning
  -
  -Each bulk item can include the version value using the
  -`version` field. It automatically follows the behavior of the
  -index / delete operation based on the `_version` mapping. It also
  -support the `version_type` (see <<index-versioning, versioning>>).
  -
  -[float]
  -[[bulk-routing]]
  -==== Routing
  -
  -Each bulk item can include the routing value using the
  -`routing` field. It automatically follows the behavior of the
  -index / delete operation based on the `_routing` mapping.
  -
  -[float]
  -[[bulk-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
  -before starting to process the bulk request. See
  -<<index-wait-for-active-shards,here>> for further details and a usage
  -example.
  -
  -[float]
  -[[bulk-refresh]]
  -==== Refresh
  -
  -Control when the changes made by this request are visible to search. See
  -<<docs-refresh,refresh>>.
  -
  -NOTE: Only the shards that receive the bulk request will be affected by
  -`refresh`. Imagine a `_bulk?refresh=wait_for` request with three
  -documents in it that happen to be routed to different shards in an index
  -with five shards. The request will only wait for those three shards to
  -refresh. The other two shards that make up the index do not
  -participate in the `_bulk` request at all.
  -
   [float]
   [[bulk-update]]
  -==== Update
  +===== Bulk update example
   
   When using the `update` action, `retry_on_conflict` can be used as a field in
   the action itself (not in the extra payload line), to specify how many
  
positive.code: --------------------------------------------------
  // TEST[continued]
  
  [float]
  [[bulk-security]]
  ==== Security
  
  See <<url-access-control>>.
  
  [float]
  [[bulk-partial-responses]]
  ==== Partial responses
  To ensure fast responses, the bulk API will respond with partial results if one or more shards fail. See <<shard-failures, Shard failures>> for more information.
negative.code: [[docs-bulk]]
  === Bulk API
  ++++
  <titleabbrev>Bulk</titleabbrev>
  ++++
  
  Performs multiple indexing or delete operations in a single API call. 
  This reduces overhead and can greatly increase indexing speed.
  
  [source,console]
  --------------------------------------------------
  