anchor.diff:  [cols="1,2"]
   |===
   | *GeoRocket-Unmerged-Chunks*
  -| The number of chunks that were skipped during merging. Possible reasons for unmerged chunks are: (1) new chunks were added to the store while merging was in progress, (2) optimistic merging was enabled and some chunks could not be merged. Based on this HTTP trailer, the client can decide whether to repeat the request to fetch the missing chunks (e.g. with optimistic merging disabled) or not. This HTTP trailer will only be sent if the request header `TE` contains the string `trailers` and if there actually were chunks that could not be merged.
  +| The number of chunks that were skipped during merging. Possible reasons for unmerged chunks are: (1) chunks were added to GeoRocket's store while merging was in progress, or (2) optimistic merging was enabled and some chunks did not fit to the search result. Based on this HTTP trailer, the client can decide whether to repeat the request to fetch the missing chunks (e.g. with optimistic merging disabled) or not. This HTTP trailer will only be sent if the request header `TE` contains the string `trailers` and if there actually were chunks that could not be merged.
   |===
   
   ===== Status codes
  
positive.code:   georocket search EQ\(key\ value\)
  
  These commands search for chunks that contain the verbatim string `EQ(key value)` and not for those where the specified property equals the given value!
  ====
  
  === Tag command
  
negative.code: [cols="1,2"]
  |===
  | *TE*
  | This header should contain the string `trailers` if GeoRocket is allowed to return HTTP trailers after the response (see the list of response trailers below).
  |===
  
  ===== Response headers
  