Index pattern fields using old types after ES index mapping change

[fpytloun]

Describe the feature:

When I change mapping that affects new indexes within datastream, Kibana index pattern fields are still using old mapping, so eg. once field type was changed from text to keyword, Kibana still things that field is not aggregatable and that it's text field.

This is not issue with field capabilities API as it returns both types properly:

{"indices":[".ds-warden-2021.06.21-000001",".ds-warden-2021.06.28-000002",".ds-warden-2021.07.05-000003",".ds-warden-2021.07.12-000004",".ds-warden-2021.07.19-000005",".ds-warden-2021.07.26-000006",".ds-warden-2021.08.02-000007",".ds-warden-2021.08.09-000008",".ds-warden-2021.08.16-000009",".ds-warden-2021.08.23-000010",".ds-warden-2021.08.30-000011",".ds-warden-2021.09.06-000012",".ds-warden-2021.09.13-000013",".ds-warden-2021.09.20-000014",".ds-warden-2021.09.27-000015",".ds-warden-2021.10.04-000016",".ds-warden-2021.10.11-000017",".ds-warden-2021.10.18-000018",".ds-warden-2021.10.25-000019",".ds-warden-2021.11.01-000020",".ds-warden-2021.11.08-000021",".ds-warden-2021.11.15-000022",".ds-warden-2021.11.22-000023",".ds-warden-2021.11.29-000024",".ds-warden-2021.12.06-000025",".ds-warden-2021.12.13-000026",".ds-warden-2021.12.20-000027",".ds-warden-2021.12.27-000028",".ds-warden-2022.01.03-000029",".ds-warden-2022.01.10-000030",".ds-warden-2022.01.17-000031",".ds-warden-2022.01.24-000032",".ds-warden-2022.01.31-000033",".ds-warden-2022.02.07-000034",".ds-warden-2022.02.14-000035",".ds-warden-2022.02.21-000036",".ds-warden-2022.02.22-000037",".ds-warden-2022.02.24-000038"],"fields":{"Endpoint":{"text":{"type":"text","metadata_field":false,"searchable":true,"aggregatable":false,"indices":[".ds-warden-2021.06.21-000001",".ds-warden-2021.06.28-000002",".ds-warden-2021.07.05-000003",".ds-warden-2021.07.12-000004",".ds-warden-2021.07.19-000005",".ds-warden-2021.07.26-000006",".ds-warden-2021.08.02-000007",".ds-warden-2021.08.09-000008",".ds-warden-2021.08.16-000009",".ds-warden-2021.08.23-000010",".ds-warden-2021.08.30-000011",".ds-warden-2021.09.06-000012",".ds-warden-2021.09.13-000013",".ds-warden-2021.09.20-000014",".ds-warden-2021.09.27-000015",".ds-warden-2021.10.04-000016",".ds-warden-2021.10.11-000017",".ds-warden-2021.10.18-000018",".ds-warden-2021.10.25-000019",".ds-warden-2021.11.01-000020",".ds-warden-2021.11.08-000021",".ds-warden-2021.11.15-000022",".ds-warden-2021.11.22-000023",".ds-warden-2021.11.29-000024",".ds-warden-2021.12.06-000025",".ds-warden-2021.12.13-000026",".ds-warden-2021.12.20-000027",".ds-warden-2021.12.27-000028",".ds-warden-2022.01.03-000029",".ds-warden-2022.01.10-000030",".ds-warden-2022.01.17-000031",".ds-warden-2022.01.24-000032",".ds-warden-2022.01.31-000033",".ds-warden-2022.02.07-000034",".ds-warden-2022.02.14-000035",".ds-warden-2022.02.21-000036"]},"keyword":{"type":"keyword","metadata_field":false,"searchable":true,"aggregatable":true,"indices":[".ds-warden-2022.02.22-000037",".ds-warden-2022.02.24-000038"]}}}}elasticsearch@elasticsearch-master-0:~$

Either Kibana should be aware of this per-index or most easily, it should use latest state. For now, this makes it impossible to change field mappings.

Using Kibana version 7.12.1

It was probably possible in the past to manually update field cache, but got changed with #82223

Describe a specific use case for the feature:

[fpytloun]

Tried Kibana 7.16.x and it works there.