anchor.diff:  BulkIndexByScrollResponse response = updateByQuery.get();
   --------------------------------------------------
   
  -`UpdateByQueryRequestBuilder` also allows you direct access to the query used
  -to select the documents which you can use to change the default scroll size or
  +`UpdateByQueryRequestBuilder` also enables direct access to the query used
  +to select the documents. You can use this access to change the default scroll size or
   otherwise modify the request for matching documents.
   
   [source,java]
  
positive.code: BulkIndexByScrollResponse response = updateByQuery.get();
  --------------------------------------------------
  
  In addition to changing the `_source` of the document (see above) the script
  can change the update action similarly to the Update API:
  
  [source,java]
  --------------------------------------------------
  
negative.code: client.admin().cluster().prepareCancelTasks().setTaskId(taskId).get().getTasks()
  --------------------------------------------------
  
  Use the `list tasks` API to find the value of `taskId`.
  
  Cancelling a request is typically a very fast process but can take up to a few seconds.
  The task status API continues to list the task until the cancellation is complete.
  
  [float]
  [[docs-update-by-query-rethrottle]]
  === Rethrottling
  
  Use the `_rethrottle` API to change the value of `requests_per_second` on a running update:
  
  [source,java]
  --------------------------------------------------
  RethrottleAction.INSTANCE.newRequestBuilder(client).setTaskId(taskId).setRequestsPerSecond(2.0f).get();
  --------------------------------------------------
  
  Use the `list tasks` API to find the value of `taskId`.
  
  As with the `updateByQuery` API, the value of `requests_per_second`
  can be any positive float value to set the level of the throttle, or `Float.POSITIVE_INFINITY` to disable throttling.
  A value of `requests_per_second` that speeds up the process takes
  effect immediately. `requests_per_second` values that slow the query take effect
  after completing the current batch in order to prevent scroll timeouts.
  