anchor.diff:  Elasticsearch will pick the best implementation based on the operating
   environment.
   
  -This can be overridden for all indices by adding this to the
  -`config/elasticsearch.yml` file:
  +The storage type can also be explicitly set for all indices by configuring the
  +store type in the `config/elasticsearch.yml` file:
   
   [source,yaml]
   ---------------------------------
  -index.store.type: niofs
  +index.store.type: hybridfs
   ---------------------------------
   
   It is a _static_ setting that can be set on a per-index basis at index
  
positive.code: == Store
  
  The store module allows you to control how index data is stored and accessed on disk.
  
  [float]
  [[file-system]]
  
negative.code: The Simple FS type is a straightforward implementation of file system
  storage (maps to Lucene `SimpleFsDirectory`) using a random access file.
  This implementation has poor concurrent performance (multiple threads
  will bottleneck) and disables some optimizations for heap memory usage.
  
  [[niofs]]`niofs`::
  
  The NIO FS type stores the shard index on the file system (maps to
  Lucene `NIOFSDirectory`) using NIO. It allows multiple threads to read
  from the same file concurrently. It is not recommended on Windows
  because of a bug in the SUN Java implementation and disables some
  optimizations for heap memory usage.
  
  [[mmapfs]]`mmapfs`::
  
  