Support new half_float and scaled_float field types

[Bargs]

Elasticsearch added a couple of new numeric datatypes, which means we
need to update our type casting list to include them. Kibana should
see them as "numbers" so they work properly in searches and aggs.

Also updates Console's list of known types

Fixes #7782
Related elastic/elasticsearch#18887
Related elastic/elasticsearch#19264

[Bargs]

@monicasarbu here's the PR to track for the new floats in Kibana

[monicasarbu]

@Bargs Thanks! It seems to work now 👍

[ycombinator]

I've verified that Kibana correctly treats the half_float and scaled_float Elasticsearch data types as numbers now:

Console autocompletes the datatypes as well. However, for the scaled_float datatype, there is an additional required parameter, scaling_factor, which Console does not offer as an autocomplete suggestion:

So the only addition needed to this PR is for Console to offer scaling_factor as an autocomplete suggestion.

[Bargs]

Good catch @ycombinator, I've pushed an update for scaling_factor autocomplete.

[Bargs]

jenkins, test this

[ycombinator]

@Bargs The scaling_factor autocomplete works. I see that it autocompletes the property's value to 100. From my testing of various properties, the convention in Console seems to be:

• If the property has a default in ES, autocomplete the property's value to that default.
• Else, autocomplete the value to a placeholder value. For example, copy_to's value autocompletes to "{field}".

From what I can tell there is no default value for scaling_factor in ES. So I'd autocomplete its value to something like {scaling_factor}, which would then require the user to replace it with an actual value.

[tsullivan]

Manually tested this in Console, created a template that uses half_float, and saw in Kibana Index Patterns that the field is mapped as number

LGTM

[spalger]

LGTM, also +1 to @ycombinator's point

[ycombinator]

Chatted with @Bargs about my comment above. He tried out my suggestion but it looks like Console code does not like autocompleting to invalid JSON values. So autocompleting the scaling_factor property's value to {scaling_factor} is not an option, at least at the moment. So it looks like the only reasonable option is to autocomplete to a number.

@Bargs is going to break out the Console part of this PR into its own so we can figure out the right thing to do there (perhaps after consulting Adrien from the ES team on what a good autocompleted number might be). That'll leave just the index pattern changes in this PR, letting us move forward with merging those.

[ycombinator]

LGTM!