Error while saving an advanced ML job

Elastic Stack Elasticsearch
1

Hello all!

I'm getting an error while saving a new 'advanced' ML job (see attached images).
I did not modify datafeed or JSON, just tried to add the detector with low_varp function over AZ field.
I tried including over_field_name as a partition by "antenna", or adding same field in "partition_field_name".
None of those ways saves ok.

image.png1007×852 45.4 KB

image.png876×418 14.1 KB

Could you please comment what is the correct way to understand the meaning of those fields?
Are these attached images enough for you to help me getting into this issue?

Thank you!
Leandro.

2

Hi Leandro,

The error is due to a mapping clash in the index where the job results are stored. By default the results from all jobs are stored in a single shared index named .ml-anomalies-shared, and that index already has a mapping for the field antenna (created by a previous job) which is different to the new mapping. Maybe previously antenna was a nested object and now is a text field.

The solution is simple: when you create the job check the Use dedicated index box and the results will be saved in a new index without any existing mappings.

1 Like
3

ok, I will try that.

Thanks, David.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.