Skip to content

Commit a4a9333

Browse files
committed
[Docs] Better Aggregation handling titles
1 parent e2f60fc commit a4a9333

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

Diff for: docs/contents/nest/aggregations/handling.markdown

+3-1
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,8 @@ The above can also be accomplished using the object initializer syntax...
4444

4545
var result = client.Search<ElasticsearchProject>(searchRequest);
4646

47+
### Getting to your aggregation
48+
4749
The result of the aggregations are accessed from the `Aggs` property of the response using the key that was specified on the request, which in the examples above would be `my_agg`:
4850

4951
var myAgg = result.Aggs.Terms("my_agg");
@@ -60,7 +62,7 @@ etc...
6062

6163
Since aggregation response structures fall into similar groups, each aggregation response in NEST is typed to a specific implementation of `IAggregationMetric`. This can be a `ValueMetric`, `SingleBucket`, `Bucket<T>`, `BucketWithDocCount<T>`, and the list goes on. The `Aggs.<Aggregation>` property of the response will automatically convert to the response from ES to the correct type.
6264

63-
### Sub-aggregations
65+
## Sub-aggregations
6466

6567
NEST of course also supports sub-aggregations...
6668

0 commit comments

Comments
 (0)