honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix summary_count_field -> summary_count_field_name typo (elastic/x-pack-elasticsearch#2588) 

Original commit: elastic/x-pack-elasticsearch@689be8c33a
This commit is contained in:
David Kyle 2017-09-21 16:44:19 +01:00
parent ce77b076ad
commit 0c96db0a1c
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/ml/aggregations.asciidoc
View File

@ -33,7 +33,7 @@ PUT _xpack/ml/anomaly_detectors/farequote
"field_name":"responsetime", "field_name":"responsetime",
"by_field_name":"airline" "by_field_name":"airline"
}], }],
"summary_count_field": "doc_count" "summary_count_field_name": "doc_count"
}, },
"data_description": { "data_description": {
"time_field":"time" "time_field":"time"

4
docs/en/ml/functions/count.asciidoc
View File

@ -89,7 +89,7 @@ compared to its past behavior.
[source,js] [source,js]
-------------------------------------------------- --------------------------------------------------
{ {
"summary_count_field" : "events_per_min", "summary_count_field_name" : "events_per_min",
"detectors" [ "detectors" [
{ "function" : "count" } { "function" : "count" }
] ]
@ -98,7 +98,7 @@ compared to its past behavior.
If you are analyzing an aggregated `events_per_min` field, do not use a sum If you are analyzing an aggregated `events_per_min` field, do not use a sum
function (for example, `sum(events_per_min)`). Instead, use the count function function (for example, `sum(events_per_min)`). Instead, use the count function
and the `summary_count_field` property. and the `summary_count_field_name` property.
//TO-DO: For more information, see <<aggreggations.asciidoc>>. //TO-DO: For more information, see <<aggreggations.asciidoc>>.
[float] [float]

2
docs/en/ml/getting-started.asciidoc
View File

@ -331,7 +331,7 @@ requests over time. It is therefore logical to start by creating a single metric
job for this KPI. job for this KPI.
TIP: If you are using aggregated data, you can create an advanced job TIP: If you are using aggregated data, you can create an advanced job
and configure it to use a `summary_count_field`. The {ml} algorithms will and configure it to use a `summary_count_field_name`. The {ml} algorithms will
make the best possible use of summarized data in this case. For simplicity, in make the best possible use of summarized data in this case. For simplicity, in
this tutorial we will not make use of that advanced functionality. this tutorial we will not make use of that advanced functionality.