Use client calls in automapping documentation

Closes #2960

(cherry picked from commit cbfd037)

Author: russcam

build/scripts/Documentation.fsx

@@ -20,7 +20,7 @@ module Documentation =
         ExecProcess (fun p ->
             p.WorkingDirectory <- Paths.Source("CodeGeneration") @@ docGenerator.Name
             p.FileName <- generator
-        ) (TimeSpan.FromMinutes 2.) |> ignore
+        ) (TimeSpan.FromMinutes 3.) |> ignore
 
     // TODO: hook documentation validation into the process
     let Validate() = 

docs/aggregations/aggregation-meta-usage.asciidoc

@@ -0,0 +1,89 @@
+:ref_current: https://www.elastic.co/guide/en/elasticsearch/reference/5.6
+
+:xpack_current: https://www.elastic.co/guide/en/x-pack/5.6
+
+:github: https://github.com/elastic/elasticsearch-net
+
+:nuget: https://www.nuget.org/packages
+
+////
+IMPORTANT NOTE
+==============
+This file has been generated from https://github.com/elastic/elasticsearch-net/tree/5.x/src/Tests/Aggregations/AggregationMetaUsageTests.cs. 
+If you wish to submit a PR for any spelling mistakes, typos or grammatical errors for this file,
+please modify the original csharp file found at the link and submit the PR with that change. Thanks!
+////
+
+[[aggregation-metadata]]
+=== Aggregation Metadata
+
+Metadata can be provided per aggregation, and will be returned in the aggregation response
+
+==== Fluent DSL example
+
+[source,csharp]
+----
+s => s
+.Size(0)
+.Aggregations(a => a
+    .Min("min_last_activity", m => m
+        .Field(p => p.LastActivity)
+        .Meta(d => d
+            .Add("meta_1", "value_1")
+            .Add("meta_2", 2)
+            .Add("meta_3", new { meta_3 = "value_3" })
+        )
+    )
+)
+----
+
+==== Object Initializer syntax example
+
+[source,csharp]
+----
+new SearchRequest<Project>()
+{
+    Size = 0,
+    Aggregations = new MinAggregation("min_last_activity", Infer.Field<Project>(p => p.LastActivity))
+    {
+        Meta = new Dictionary<string,object>
+        {
+            { "meta_1", "value_1" },
+            { "meta_2", 2 },
+            { "meta_3", new { meta_3 = "value_3" } }
+        }
+    }
+}
+----
+
+[source,javascript]
+.Example json output
+----
+{
+  "size": 0,
+  "aggs": {
+    "min_last_activity": {
+      "min": {
+        "field": "lastActivity"
+      },
+      "meta": {
+        "meta_1": "value_1",
+        "meta_2": 2,
+        "meta_3": {
+          "meta_3": "value_3"
+        }
+      }
+    }
+  }
+}
+----
+
+==== Handling Responses
+
+[source,csharp]
+----
+response.ShouldBeValid();
+var min = response.Aggs.Min("min_last_activity");
+min.Meta.Should().NotBeNull().And.ContainKeys("meta_1", "meta_2", "meta_3");
+----
+

docs/client-concepts/high-level/mapping/attribute-mapping.asciidoc

@@ -76,11 +76,12 @@ Then we map the types by calling `.AutoMap()`
 
 [source,csharp]
 ----
-var descriptor = new CreateIndexDescriptor("myindex")
+var createIndexResponse = client.CreateIndex("myindex", c => c
     .Mappings(ms => ms
         .Map<Company>(m => m.AutoMap())
         .Map<Employee>(m => m.AutoMap())
-    );
+    )
+);
 ----
 
 [source,javascript]

docs/client-concepts/high-level/mapping/auto-map.asciidoc

@@ -51,16 +51,19 @@ on the POCO
 
 [source,csharp]
 ----
-var descriptor = new CreateIndexDescriptor("myindex")
+var createIndexResponse = client.CreateIndex("myindex", c => c
     .Mappings(ms => ms
         .Map<Company>(m => m.AutoMap()) <1>
         .Map<Employee>(m => m.AutoMap()) <2>
-    );
+    )
+);
 ----
 <1> Auto map `Company`
 
 <2> Auto map `Employee`
 
+This produces the following JSON request
+
 [source,javascript]
 ----
 {
@@ -159,6 +162,51 @@ var descriptor = new CreateIndexDescriptor("myindex")
 }
 ----
 
+[source,csharp]
+----
+var connectionSettings = new ConnectionSettings(new InMemoryConnection()) <1>
+    .DisableDirectStreaming() <2>
+    .InferMappingFor<ParentWithStringId>(m => m
+        .TypeName("parent")
+        .Ignore(p => p.Description)
+        .Ignore(p => p.IgnoreMe)
+    );
+
+var client = new ElasticClient(connectionSettings);
+
+var createIndexResponse = client.CreateIndex("myindex", c => c
+    .Mappings(ms => ms
+        .Map<ParentWithStringId>(m => m
+            .AutoMap()
+        )
+    )
+    );
+----
+<1> we're using an _in memory_ connection for this example. In your production application though, you'll want to use an `IConnection` that actually sends a request.
+
+<2> we disable direct streaming here to capture the request and response bytes. In your production application however, you'll likely not want to do this, since it causes the request and response bytes to be buffered in memory.
+
+[source,javascript]
+----
+{
+  "mappings": {
+    "parent": {
+      "properties": {
+        "id": {
+          "type": "text",
+          "fields": {
+            "keyword": {
+              "ignore_above": 256,
+              "type": "keyword"
+            }
+          }
+        }
+      }
+    }
+  }
+}
+----
+
 Observe that NEST has inferred the Elasticsearch types based on the CLR type of our POCO properties.
 In this example,
 
@@ -177,57 +225,105 @@ sub field.
 
 NEST has inferred mapping support for the following .NET types
 
-* `String` maps to `"text"` with a `"keyword"` sub field. See <<multi-fields, Multi Fields>>.
+[horizontal]
+`String`::
+
+maps to `"text"` with a `"keyword"` sub field. See <<multi-fields, Multi Fields>>.
+
+`Int32`::
+
+maps to `"integer"`
+
+`UInt16`::
+
+maps to `"integer"`
+
+`Int16`::
+
+maps to `"short"`
+
+`Byte`::
+
+maps to `"short"`
+
+`Int64`::
+
+maps to `"long"`
+
+`UInt32`::
 
-* `Int32` maps to `"integer"`
+maps to `"long"`
 
-* `UInt16` maps to `"integer"`
+`TimeSpan`::
 
-* `Int16` maps to `"short"`
+maps to `"long"`
 
-* `Byte` maps to `"short"`
+`Single`::
 
-* `Int64` maps to `"long"`
+maps to `"float"`
 
-* `UInt32` maps to `"long"`
+`Double`::
 
-* `TimeSpan` maps to `"long"`
+maps to `"double"`
 
-* `Single` maps to `"float"`
+`Decimal`::
 
-* `Double` maps to `"double"`
+maps to `"double"`
 
-* `Decimal` maps to `"double"`
+`UInt64`::
 
-* `UInt64` maps to `"double"`
+maps to `"double"`
 
-* `DateTime` maps to `"date"`
+`DateTime`::
 
-* `DateTimeOffset` maps to `"date"`
+maps to `"date"`
 
-* `Boolean` maps to `"boolean"`
+`DateTimeOffset`::
 
-* `Char` maps to `"keyword"`
+maps to `"date"`
 
-* `Guid` maps to `"keyword"`
+`Boolean`::
+
+maps to `"boolean"`
+
+`Char`::
+
+maps to `"keyword"`
+
+`Guid`::
+
+maps to `"keyword"`
 
 and supports a number of special types defined in NEST
 
-* `Nest.GeoLocation` maps to `"geo_point"`
+[horizontal]
+`Nest.GeoLocation`::
+
+maps to `"geo_point"`
+
+`Nest.CompletionField`::
 
-* `Nest.CompletionField` maps to `"completion"`
+maps to `"completion"`
 
-* `Nest.Attachment` maps to `"attachment"`
+`Nest.DateRange`::
 
-* `Nest.DateRange` maps to `"date_range"`
+maps to `"date_range"`
 
-* `Nest.DoubleRange` maps to `"double_range"`
+`Nest.DoubleRange`::
 
-* `Nest.FloatRange` maps to `"float_range"`
+maps to `"double_range"`
 
-* `Nest.IntegerRange` maps to `"integer_range"`
+`Nest.FloatRange`::
 
-* `Nest.LongRange` maps to `"long_range"`
+maps to `"float_range"`
+
+`Nest.IntegerRange`::
+
+maps to `"integer_range"`
+
+`Nest.LongRange`::
+
+maps to `"long_range"`
 
 All other types map to `"object"` by default.
 
@@ -282,10 +378,11 @@ By default, `.AutoMap()` only goes as far as depth 1
 
 [source,csharp]
 ----
-var descriptor = new CreateIndexDescriptor("myindex")
+var createIndexResponse = client.CreateIndex("myindex", c => c
     .Mappings(ms => ms
         .Map<A>(m => m.AutoMap())
-    );
+    )
+);
 ----
 
 Thus we do not map properties on the second occurrence of our Child property 
@@ -310,10 +407,11 @@ Now let's specify a maxRecursion of `3`
 
 [source,csharp]
 ----
-var withMaxRecursionDescriptor = new CreateIndexDescriptor("myindex")
+createIndexResponse = client.CreateIndex("myindex", c => c
     .Mappings(ms => ms
         .Map<A>(m => m.AutoMap(3))
-    );
+    )
+);
 ----
 
 `.AutoMap()` has now mapped three levels of our Child property