Index patterns do not support `date_range` ES type

[andrewvc]

master (as of Sep. 8, 2020)

When using heartbeat' which specifies a date range field for monitor.timespan, there are errors when reloading the index pattern. See SS below:

It appears Kibana cannot handle these types

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[briancurtin]

I'm not sure if or how relevant this is, but in https://github.com/elastic/cloud/pull/77418 we had a case where we have a mapping with {"range": "date_range"} and we seeded some tests with data in an index before explicitly creating a mapping. That resulted in Elasticsearch dynamically creating a mapping that resulted in fields like {"range.gte": "date", "range.lt": "date"}, so I was able to create an Index Pattern for range.gte nicely. Then we noticed we were indexing that test data without the full mapping which caused other issues, so now we create the mapping, index the test data, and then we're good...but we then lost the ability to have a date field on the pattern. The referenced change is for us to add a standalone {"timestamp": "date"} field that is a duplicate of the range.gte contents.

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

I've just checked in Discover, Data view management, date_range ES type is now supported correctly

Thx for a lot for reporting , sorry for the long delay, seems it was lost in issue flood.