anchor.diff:          "name":["New York City"],
           "countrycode":["US"]}]
     }}
  -....
  -
  -[[tagger-tips]]
  -== Tips
  +----
  +
  +== Tagger Tips
   
   Performance Tips:
   
  
positive.code: population.
  
  Using bin/post:
  ....
  bin/post -c geonames -type text/csv \
    -params 'optimize=true&separator=%09&encapsulator=%00&fieldnames=id,name,,alternative_names,latitude,longitude,,,countrycode,,,,,,population,elevation,,timezone,lastupdate' \
    /tmp/cities1000.txt
  ....
  or using curl:
  ....
  curl -X POST --data-binary @/path/to/cities1000.txt -H 'Content-type:application/csv' \
    'http://localhost:8983/solr/geonames/update?commit=true&optimize=true&separator=%09&encapsulator=%00&fieldnames=id,name,,alternative_names,latitude,longitude,,,countrycode,,,,,,population,elevation,,timezone,lastupdate'
  ....
  
  That might take around 35 seconds; it depends. It can be a lot faster if
  the schema were tuned to only have what we truly need (no text search if
  not needed).
  
  In that command we said optimize=true to put the index in a state that
  will make tagging faster. The encapsulator=%00 is a bit of a hack to
  disable the default double-quote.
  
  [[tagger-tag-time]]
  === Tag Time!
  
  This is a trivial example tagging a small piece of text. For more
  options, see the earlier documentation.
  
  ....
  curl -X POST \
    'http://localhost:8983/solr/geonames/tag?overlaps=NO_SUB&tagsLimit=5000&fl=id,name,countrycode&wt=json&indent=on' \
    -H 'Content-Type:text/plain' -d 'Hello New York City'
  ....
  
  The response should be this (the QTime may vary):
  
  ....
  {
    "responseHeader":{
      "status":0,
  
negative.code:      You'll need to keep track of the character offsets of these so you can subtract them from the results.
  ** For reducing tagging latency even further, consider embedding Solr with `EmbeddedSolrServer`.
     See `EmbeddedSolrNoSerializeTest`.
  ** Use more than one thread -- perhaps as many as there are CPU cores available to Solr.
  