You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new field type unsigned_long was added to Elasticsearch in elastic/elasticsearch#60050 and core Kibana in #81115. This is a new type of numeric field. The necessary changes for the ML Java data frame analytics code to work with unsigned_long were made in elastic/elasticsearch#64066. Given that this type is supported in core Kibana now it could be argued that it is now a bug that it's not supported in the ML UI.
I did some testing with the ML Java changes combined with the following Kibana patch:
With those changes the unsigned_long fields showed up as expected when creating a new data frame analytics job, and it was possible to run that job and view the results. However, in the results grid the unsigned_long fields did not show up. So it seems that some other change is also needed. However, hopefully it is not a massive amount of work to add support for unsigned_long to the data frame analytics UI.
The text was updated successfully, but these errors were encountered:
I'll just add a note and screenshot from the testing I did on 7.10.0. I created an index pattern with 4 docs which have an unsigned long field "my_counter" which shows a value rounded or truncated to the precision Kibana supports, and also has a string representation of the actual value "string_counter". The values of "my_counter" do appear in the grid view;
But when I click the Outlier detection selection I get an error.
A new field type
unsigned_long
was added to Elasticsearch in elastic/elasticsearch#60050 and core Kibana in #81115. This is a new type of numeric field. The necessary changes for the ML Java data frame analytics code to work withunsigned_long
were made in elastic/elasticsearch#64066. Given that this type is supported in core Kibana now it could be argued that it is now a bug that it's not supported in the ML UI.I did some testing with the ML Java changes combined with the following Kibana patch:
With those changes the
unsigned_long
fields showed up as expected when creating a new data frame analytics job, and it was possible to run that job and view the results. However, in the results grid theunsigned_long
fields did not show up. So it seems that some other change is also needed. However, hopefully it is not a massive amount of work to add support forunsigned_long
to the data frame analytics UI.The text was updated successfully, but these errors were encountered: