anchor.diff:  --------------------------------------------------
   // TEST[continued]
   
  -The reload request returns information about the nodes it was executed on and the
  -analyzers that were reloaded:
  +The API returns the following response.
   
   [source,console-result]
   --------------------------------------------------
  
positive.code:             "text": {
                  "type": "text",
                  "analyzer" : "standard",
                  "search_analyzer": "my_synonyms" <2>
              }
          }
      }
  }
  --------------------------------------------------
  
  <1> Mark the synonym filter as updateable.
  <2> Synonym analyzer is usable as a search_analyzer.
  
  NOTE: Trying to use the above analyzer as an index analyzer will result in an error.
  
  Using the <<indices-reload-analyzers,analyzer reload API>>, you can trigger reloading of the
  synonym definition. The contents of the configured synonyms file will be reloaded and the
  synonyms definition the filter uses will be updated. 
  
  The `_reload_search_analyzers` API can be run on one or more indices and will trigger 
  reloading of the synonyms from the configured file.
  
  NOTE: Reloading will happen on every node the index has shards, so its important
  to update the synonym file contents on every data node (even the ones that don't currently
  hold shard copies; shards might be relocated there in the future) before calling
  reload to ensure the new state of the file is reflected everywhere in the cluster.
  
  [source,console]
  --------------------------------------------------
  
negative.code: // TESTRESPONSE[s/"total" : 2/"total" : $body._shards.total/]
  // TESTRESPONSE[s/"successful" : 2/"successful" : $body._shards.successful/]
  // TESTRESPONSE[s/mfdqTXn_T7SGr2Ho2KT8uw/$body.reload_details.0.reloaded_node_ids.0/]
  