anchor.diff:  See the {ref}/freeze-index-api.html[freeze API].
   // end::freeze-def[]
   
  +[[glossary-frozen-index]] frozen index ::  
  +// tag::frozen-index-def[]
  +An index reduced to a low overhead state that still enables occasional searches.
  +Frozen indices use a memory-efficient shard implementation and throttle searches to conserve resources.
  +Searching a frozen index is lower overhead than re-opening a closed index to enable searching.
  +// end::frozen-index-def[]
  +
  +[[glossary-hot-phase]] hot phase ::
  +// tag::hot-phase-def[]
  +The first possible phase in the <<glossary-index-lifecycle,index lifecycle>>. 
  +In the hot phase, an index is actively updated and queried. 
  +// end::hot-phase-def[]
  +
   [[glossary-id]] id ::
   // tag::id-def[]
   The ID of a <<glossary-document,document>> identifies a document. The
  
positive.code: In most cases, the goal of filtering is to reduce the number of documents that have to be examined.
  // end::filter-def[]
  
  [[glossary-follower-index]] follower index ::  
  // tag::follower-index-def[]
  Follower indices are the target indices for <<glossary-ccr,{ccr}>>. They exist
  in your local cluster and replicate <<glossary-leader-index,leader indices>>.
  // end::follower-index-def[]
  
  [[glossary-force-merge]] force merge ::  
  
negative.code: +
  --
  // tag::index-def[]
  // tag::index-def-short[]
  An optimized collection of JSON documents. Each document is a collection of fields, 
  the key-value pairs that contain your data. 
  // end::index-def-short[]
  
  An index is a logical namespace that maps to one or more
  <<glossary-primary-shard,primary shards>> and can have zero or more
  <<glossary-replica-shard,replica shards>>.
  // end::index-def[]
  