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.

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

[ML] Anomaly detector job validation fails if time field is of type date_nanos #52921

Closed
davidkyle opened this issue Dec 12, 2019 · 1 comment · Fixed by #59017
Closed

[ML] Anomaly detector job validation fails if time field is of type date_nanos #52921

davidkyle opened this issue Dec 12, 2019 · 1 comment · Fixed by #59017
Assignees

Comments

@davidkyle
Copy link
Member

Describe the feature:
In v7.5 you cannot create a job on data that has a time field of datatype date_nanos, the validation step will error with:

'time' cannot be used as the time-field because it's not a valid field of type 'date'.

On the back end there is no reason why anomaly detectors wouldn't work with the date_nanos datatype and it is possible to use if you create the job and datafeed using the APIs rather than kibana.

Originally raised in elastic/elasticsearch#49889

@davidkyle davidkyle added the Feature:Anomaly Detection ML anomaly detection label Dec 12, 2019
@peteharverson peteharverson changed the title Support the data_nanos datatype in anomaly detector jobs [ML] Support the data_nanos datatype in anomaly detector jobs Dec 16, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@peteharverson peteharverson changed the title [ML] Support the data_nanos datatype in anomaly detector jobs [ML] Support the date_nanos datatype in anomaly detector jobs Dec 19, 2019
@peteharverson peteharverson changed the title [ML] Support the date_nanos datatype in anomaly detector jobs [ML] Anomaly detector job validation fails if time field is of type date_nanos Dec 19, 2019
@peteharverson peteharverson self-assigned this Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants