title: Pass update_all_types on ElasticSearch Put Mapping
body: <p>We are upgrading to ElasticSearch 2.0 and have come across an issue with our mappings in Nest 1.7.0 : we have two types that share a field (with the same format):</p>
  
  <pre><code>"@timestamp": {
              "type": "date",
              "format": "epoch_millis||dateOptionalTime"
            }
  </code></pre>
  
  <p>When we try to add a mapping on startup for one of the affected types (we are currently <code>PUT</code>ing the mappings every time), we get this error back:</p>
  
  <pre><code>{
    "error": {
      "root_cause": [{
        "type": "merge_mapping_exception",
        "reason": "Merge failed with failures {[mapper [@timestamp] is used by multiple types. Set update_all_types to true to update [format] across all types.]}"
      }],
      "type": "merge_mapping_exception",
      "reason": "Merge failed with failures {[mapper [@timestamp] is used by multiple types. Set update_all_types to true to update [format] across all types.]}"
    },
    "status": 400
  }
  </code></pre>
  
  <p>We are using a code based mapping described <a href="https://nest.azurewebsites.net/nest/indices/put-mapping.html" rel="nofollow">here</a>, but I do not see a way of hanging a query string off of this method without resorting to the <code>Raw</code> property of our client using something like this:</p>
  
  <p><code>_client.Raw.IndicesPutMapping("ourindex", "ourtype", PutMappingDescriptorObj, parameters =&gt; parameters.AddQueryString("update_all_types", null));</code></p>
  
  <p>I've browsed the <a href="https://github.com/elastic/elasticsearch-net/tree/2.0" rel="nofollow">2.0 branch</a> of Nest, but have not found any references to this update_all_types query string parameter for these mapping calls.</p>
  
  <p>Assuming that <code>IndicesPutMapping()</code> call could be made to work, is that our only option at this point? I am starting to wonder if we should instead only conditionally add these mappings.</p>