Regenerate documentation

Author: codebrain

docs/aggregations.asciidoc

@@ -66,6 +66,8 @@ The values are typically extracted from the fields of the document (using the fi
 
 * <<top-hits-aggregation-usage,Top Hits Aggregation Usage>>
 
+* <<top-metrics-aggregation-usage,Top Metrics Aggregation Usage>>
+
 * <<value-count-aggregation-usage,Value Count Aggregation Usage>>
 
 * <<weighted-average-aggregation-usage,Weighted Average Aggregation Usage>>
@@ -106,6 +108,8 @@ include::aggregations/metric/sum/sum-aggregation-usage.asciidoc[]
 
 include::aggregations/metric/top-hits/top-hits-aggregation-usage.asciidoc[]
 
+include::aggregations/metric/top-metrics/top-metrics-aggregation-usage.asciidoc[]
+
 include::aggregations/metric/value-count/value-count-aggregation-usage.asciidoc[]
 
 include::aggregations/metric/weighted-average/weighted-average-aggregation-usage.asciidoc[]

docs/aggregations/bucket/parent/parent-aggregation-usage.asciidoc

@@ -47,6 +47,7 @@ new ParentAggregation("name_of_parent_agg", typeof(CommitActivity)) <1>
 }
 ----
 <1> `join` field is determined from the _child_ type. In this example, it is `CommitActivity`
+
 <2> sub-aggregations are on the type determined from the `join` field. In this example, a `Project` is a parent of `CommitActivity`
 
 [source,javascript]

docs/aggregations/metric/boxplot/boxplot-aggregation-usage.asciidoc

@@ -1,4 +1,4 @@
-:ref_current: https://www.elastic.co/guide/en/elasticsearch/reference/master
+:ref_current: https://www.elastic.co/guide/en/elasticsearch/reference/7.7
 
 :github: https://github.com/elastic/elasticsearch-net
 
@@ -7,7 +7,7 @@
 ////
 IMPORTANT NOTE
 ==============
-This file has been generated from https://github.com/elastic/elasticsearch-net/tree/master/src/Tests/Tests/Aggregations/Metric/Boxplot/BoxplotAggregationUsageTests.cs. 
+This file has been generated from https://github.com/elastic/elasticsearch-net/tree/7.x/src/Tests/Tests/Aggregations/Metric/Boxplot/BoxplotAggregationUsageTests.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!
 ////

docs/aggregations/metric/top-metrics/top-metrics-aggregation-usage.asciidoc

@@ -0,0 +1,93 @@
+:ref_current: https://www.elastic.co/guide/en/elasticsearch/reference/7.7
+
+: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/7.x/src/Tests/Tests/Aggregations/Metric/TopMetrics/TopMetricsAggregationUsageTests.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!
+////
+
+[[top-metrics-aggregation-usage]]
+=== Top Metrics Aggregation Usage
+
+The top metrics aggregation selects metrics from the document with the largest or smallest "sort" value.
+
+Top metrics is fairly similar to "top hits" in spirit but because it is more limited it is able to do its job using less memory and is often faster.
+
+Be sure to read the Elasticsearch documentation on {ref_current}/search-aggregations-metrics-top-metrics.html[Top Metrics Aggregation]
+
+==== Fluent DSL example
+
+[source,csharp]
+----
+a => a
+.TopMetrics("tm", st => st
+    .Metrics(m => m.Field(p => p.NumberOfContributors))
+    .Size(10)
+    .Sort(sort => sort
+        .Ascending("numberOfContributors")
+    )
+)
+----
+
+==== Object Initializer syntax example
+
+[source,csharp]
+----
+new TopMetricsAggregation("tm")
+{
+    Metrics = new List<ITopMetricsValue>
+    {
+        new TopMetricsValue(Field<Project>(p => p.NumberOfContributors))
+    },
+    Size = 10,
+    Sort = new List<ISort> { new FieldSort { Field = "numberOfContributors", Order = SortOrder.Ascending } }
+}
+----
+
+[source,javascript]
+.Example json output
+----
+{
+  "tm": {
+    "top_metrics": {
+      "metrics": [
+        {
+          "field": "numberOfContributors"
+        }
+      ],
+      "size": 10,
+      "sort": [
+        {
+          "numberOfContributors": {
+            "order": "asc"
+          }
+        }
+      ]
+    }
+  }
+}
+----
+
+==== Handling Responses
+
+[source,csharp]
+----
+response.ShouldBeValid();
+var topMetrics = response.Aggregations.TopMetrics("tm");
+topMetrics.Should().NotBeNull();
+topMetrics.Top.Should().NotBeNull();
+topMetrics.Top.Count.Should().BeGreaterThan(0);
+
+var tipTop = topMetrics.Top.First();
+tipTop.Sort.Should().Should().NotBeNull();
+tipTop.Sort.Count.Should().BeGreaterThan(0);
+tipTop.Metrics.Should().NotBeNull();
+tipTop.Metrics.Count.Should().BeGreaterThan(0);
+----
+

docs/aggregations/writing-aggregations.asciidoc

@@ -232,6 +232,7 @@ return s => s
         );
 ----
 <1> a list of aggregation functions to apply
+
 <2> Using LINQ's `Aggregate()` function to accumulate/apply all of the aggregation functions
 
 [[handling-aggregate-response]]
@@ -275,5 +276,6 @@ var maxPerChild = childAggregation.Max("max_per_child");
 maxPerChild.Should().NotBeNull(); <2>
 ----
 <1> Do something with the average per child. Here we just assert it's not null
+
 <2> Do something with the max per child. Here we just assert it's not null
 

docs/client-concepts/connection-pooling/building-blocks/connection-pooling.asciidoc

@@ -97,6 +97,7 @@ var pool = new CloudConnectionPool(cloudId, credentials); <2>
 var client = new ElasticClient(new ConnectionSettings(pool));
 ----
 <1> a username and password that can access Elasticsearch service on Elastic Cloud
+
 <2> `cloudId` is a value that can be retrieved from the Elastic Cloud web console
 
 This type of pool, like its parent the `SingleNodeConnectionPool`, is hardwired to opt out of

docs/client-concepts/connection-pooling/exceptions/unexpected-exceptions.asciidoc

@@ -58,8 +58,11 @@ audit = await audit.TraceUnexpectedException(
 );
 ----
 <1> set up a cluster with 10 nodes
+
 <2> where node 2 on port 9201 always throws an exception
+
 <3> The first call to 9200 returns a healthy response
+
 <4> ...but the second call, to 9201, returns a bad response
 
 Sometimes, an unexpected exception happens further down in the pipeline. In this scenario, we
@@ -98,7 +101,9 @@ audit = await audit.TraceUnexpectedException(
 );
 ----
 <1> calls on 9200 set up to throw a `HttpRequestException` or a `WebException`
+
 <2> calls on 9201 set up to throw an `Exception`
+
 <3> Assert that the audit trail for the client call includes the bad response from 9200 and 9201
 
 An unexpected hard exception on ping and sniff is something we *do* try to recover from and failover to retrying on the next node.
@@ -143,6 +148,8 @@ audit = await audit.TraceUnexpectedException(
 );
 ----
 <1> `InnerException` is the exception that brought the request down
+
 <2> The hard exception that happened on ping is still available though
+
 <3> An exception can be hard to relate back to a point in time, so the exception is also available on the audit trail
 

docs/client-concepts/connection-pooling/exceptions/unrecoverable-exceptions.asciidoc

@@ -81,6 +81,7 @@ var audit = new Auditor(() => VirtualClusterWith
 );
 ----
 <1> Always succeed on ping
+
 <2> ...but always fail on calls with a 401 Bad Authentication response
 
 Now, let's make a client call. We'll see that the first audit event is a successful ping
@@ -101,7 +102,9 @@ audit = await audit.TraceElasticsearchException(
 );
 ----
 <1> First call results in a successful ping
+
 <2> Second call results in a bad response
+
 <3> The reason for the bad response is Bad Authentication
 
 When a bad authentication response occurs, the client attempts to deserialize the response body returned;
@@ -135,6 +138,7 @@ audit = await audit.TraceElasticsearchException(
 );
 ----
 <1> Always return a 401 bad response with a HTML response on client calls
+
 <2> Assert that the response body bytes are null
 
 Now in this example, by turning on `DisableDirectStreaming()` on `ConnectionSettings`, we see the same behaviour exhibited
@@ -169,5 +173,6 @@ audit = await audit.TraceElasticsearchException(
 );
 ----
 <1> Response bytes are set on the response
+
 <2> Assert that the response contains `"nginx/"`
 

docs/client-concepts/connection-pooling/request-overrides/disable-sniff-ping-per-request.asciidoc

@@ -65,8 +65,11 @@ audit = await audit.TraceCalls(
 );
 ----
 <1> disable sniffing
+
 <2> first call is a successful ping
+
 <3> sniff on startup call happens here, on the second call
+
 <4> No sniff on startup again
 
 Now, let's disable pinging on the request 
@@ -90,6 +93,7 @@ audit = await audit.TraceCall(
 );
 ----
 <1> disable ping
+
 <2> No ping after sniffing
 
 Finally, let's demonstrate disabling both sniff and ping on the request 
@@ -111,5 +115,6 @@ audit = await audit.TraceCall(
 );
 ----
 <1> disable ping and sniff
+
 <2> no ping or sniff before the call
 

docs/client-concepts/connection-pooling/round-robin/skip-dead-nodes.asciidoc

@@ -140,7 +140,9 @@ await audit.TraceCalls(
 );
 ----
 <1> The first call goes to 9200 which succeeds
+
 <2> The 2nd call does a ping on 9201 because its used for the first time. It fails so we wrap over to node 9202
+
 <3> The next call goes to 9203 which fails so we should wrap over
 
 A cluster with 2 nodes where the second node fails on ping 
@@ -191,5 +193,6 @@ await audit.TraceCalls(
 );
 ----
 <1> All the calls fail
+
 <2> After all our registered nodes are marked dead we want to sample a single dead node each time to quickly see if the cluster is back up. We do not want to retry all 4 nodes