From 0365edbae0e19fb982eeb2dc02d1fed59c7d5543 Mon Sep 17 00:00:00 2001 From: lcawl Date: Mon, 20 Jan 2020 10:52:47 -0800 Subject: [PATCH] [DOCS] Adds ML limitation for date_nanos --- .../stack/ml/anomaly-detection/limitations.asciidoc | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/en/stack/ml/anomaly-detection/limitations.asciidoc b/docs/en/stack/ml/anomaly-detection/limitations.asciidoc index b68ed6aeb..8c16ef386 100644 --- a/docs/en/stack/ml/anomaly-detection/limitations.asciidoc +++ b/docs/en/stack/ml/anomaly-detection/limitations.asciidoc @@ -245,4 +245,13 @@ In 6.6 and later releases, the {ref}/ml-get-job.html[get jobs API] and the jobs. Likewise, the {ref}/ml-get-datafeed.html[get {dfeeds} API] and the {ref}/ml-get-datafeed-stats.html[get {dfeed} statistics API] return a maximum of 10,000 {dfeeds}. - \ No newline at end of file + +[float] +[[ml-limitations-nanos]] +=== Date nanoseconds data types are not supported +// https://github.com/elastic/elasticsearch/issues/49889 + +When you create an {anomaly-job}, you cannot use a field with the +{ref}/date_nanos.html[`date_nanos` data type] as the `time_field` in the +`data_description` object. This limitation applies irrespective of whether you +create jobs in {kib} or by using APIs. \ No newline at end of file