anchor.diff:  '
   --------------------------------------------------
   
  -Note above that for the delete action, there is no corresponding source document after it since deletes only require the ID of the document to be deleted.
  -
  -The bulk API executes all the actions sequentially and in order. If a single action fails for whatever reason, it will continue to process the remainder of the actions after it. When the bulk API returns, it will provide a status for each action (in the same order it was sent in) so that you can check if a specific action failed or not.
  -
  -== Exploring Your Data
  +注意到上面命令中的删除操作, 它后面没有相应的源文档, 因为删除操作只需要要删除文档的ID.
  +
  +批处理API依次并按顺序执行所有的操作. 无论出于何原因, 如果单个操作失败了, 它会继续执行后面剩余的操作.
  +当批处理API返回时, 它会为每个操作提供执行状态信息 (与发送时操作的顺序相同), 这样你就可以检查某个特定的操作是否失败.
  +
  +== 数据检索
   
   [float]
  -=== Sample Dataset
  -
  -Now that we've gotten a glimpse of the basics, let's try to work on a more realistic dataset. I've prepared a sample of fictitious JSON documents of customer bank account information. Each document has the following schema:
  +=== 示例数据集
  +
  +现在我们已经粗略的看了一些基础知识, 让我们尝试一个更加真实的数据集.我已经准备好了虚构的顾客银行账户信息的JSON文档样本.
  +每个文档都有以下schema:
   
   [source,sh]
   --------------------------------------------------
  
positive.code: }'
  --------------------------------------------------
  
  The above changes the name of the document with the ID of 1 from "John Doe" to "Jane Doe". If, on the other hand, we use a different ID, a new document will be indexed and the existing document(s) already in the index remains untouched.
  
  [source,sh]
  --------------------------------------------------
  
negative.code: }'
  --------------------------------------------------
  
  现在我们介绍一下 <<query-dsl-bool-query,`bool`(ean) query>>. `bool` 查询允许我们使用布尔逻辑来将较小的查询组合成较大的查询.
  
  下面的示例由两个 `match` 查询组成并返回地址中包含 "mill" 和 "lane" 的所有账户:
  
  [source,sh]
  --------------------------------------------------
  