anchor.diff:  BulkIndexByScrollResponse response = updateByQuery.get();
   --------------------------------------------------
   
  -Just as in <<docs-update,Update API>> you can set `ctx.op` to change the
  -operation that is executed:
  +As in the <<docs-update,Update API>>, you can set the value of `ctx.op` to change the
  +operation that executes:
   
   `noop`::
   
  -Set `ctx.op = "noop"` if your script decides that it doesn't have to make any
  -changes. That will cause `updateByQuery` to omit that document from its updates.
  - This no operation will be reported in the `noop` counter in the
  +Set `ctx.op = "noop"` if your script doesn't make any
  +changes. The `updateByQuery` operaton then omits that document from the updates.
  +This behavior increments the `noop` counter in the
   <<docs-update-by-query-response-body, response body>>.
   
   `delete`::
  
positive.code: client.admin().cluster().prepareCancelTasks().setTaskId(taskId).get().getTasks()
  --------------------------------------------------
  
  The `taskId` can be found using the list tasks API above.
  
  Cancelation should happen quickly but might take a few seconds. The task status
  API above will continue to list the task until it is wakes to cancel itself.
  
  
  [float]
  [[docs-update-by-query-rethrottle]]
  === Rethrottling
  
  The value of `requests_per_second` can be changed on a running update by query
  using the `_rethrottle` API:
  
  [source,java]
  --------------------------------------------------
  RethrottleAction.INSTANCE.newRequestBuilder(client).setTaskId(taskId).setRequestsPerSecond(2.0f).get();
  --------------------------------------------------
  
  The `taskId` can be found using the tasks API above.
  
  Just like when setting it on the `updateByQuery` API `requests_per_second`
  can be either `Float.POSITIVE_INFINITY` to disable throttling or any positive
  float to throttle to that level. Rethrottling that speeds up the query takes
  effect immediately but rethrotting that slows down the query will take effect
  on after completing the current batch. This prevents scroll timeouts.
  
negative.code: deleted. The deletion will be reported in the `deleted` counter in the
  <<docs-update-by-query-response-body, response body>>.
  
  Setting `ctx.op` to any other value generates an error. Setting any
  other field in `ctx` generates an error.
  
  This API doesn't allow you to move the documents it touches, just modify their
  source. This is intentional! We've made no provisions for removing the document
  from its original location.
  
  You can also perform these operations on multiple indices and types at once, similar to the search API:
  
  [source,java]
  --------------------------------------------------
  