In Kibana 7, users won't be able to create Index Pattern because, as it turned out, Quesma response to _field_caps request does not have the expected Content-Type header.
This is the screen after Index Pattern creation which in fact failed under the hood:
Whenever we'll try using that in "Discover" we'll end up with even more errors:
At first I've thought that there were some breaking changes in the _field_caps endpoint in Elasticsearch 8. Well, the response is indeed different, but as most of the changes were additive it looks like we can get away with 8-style response returned to Kibana 7 (🍾!).
At this moment we support Kibana 8.x and OSD.
In Kibana 7, users won't be able to create Index Pattern because, as it turned out, Quesma response to
_field_capsrequest does not have the expectedContent-Typeheader.This is the screen after Index Pattern creation which in fact failed under the hood:
Whenever we'll try using that in "Discover" we'll end up with even more errors:
At first I've thought that there were some breaking changes in the
_field_capsendpoint in Elasticsearch 8. Well, the response is indeed different, but as most of the changes were additive it looks like we can get away with 8-style response returned to Kibana 7 (🍾!).