Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Adds ML limitation for date_nanos #815

Merged
merged 1 commit into from
Jan 22, 2020
Merged

[DOCS] Adds ML limitation for date_nanos #815

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion docs/en/stack/ml/anomaly-detection/limitations.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}.


[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.