Support runtime fields defined in an ES mapping

[stacey-gammon]

Runtime fields will soon be addable to an ES index mapping: elastic/elasticsearch#59332. The first phase is to ensure these fields work as expected when they are added to an index mapping. Each area in Kibana should:

• Investigate whether the known API differences will affect their application
• Test their assumptions
• Document and discuss any limitations

Testing & investigation needed by teams:

• Analyze
  • Discover (In Discover, be able to show doc_values for any field not stored #64878), Lens, Visualize, TSVB
  • Query bar, filters and Search APIs
  • Canvas
  • ML
  • Maps [Maps] Support runtime fields #77070
• Observability
  • Logs ([Logs UI] Support mappings-based runtime fields in the Logs UI #74937)
  • APM
  • Uptime
• Enterprise search
• Security/SIEM
• Elasticsearch UI
• App architecture

Known issues:

• Discover will show blank values due to accessing field values off source: In Discover, be able to show doc_values for any field not stored #64878
• Logs UI also accessing field values off source: [Logs UI] Support mappings-based runtime fields in the Logs UI #74937

[cjcenizal]

Thanks for calling these out @stacey-gammon! We're OK on both of this items.

Runtime fields specified in a filter query when creating an index alias will cause the request to fail.

We don't have any UIs that consume this API, except for Console.

When creating an index, runtime fields specified in index sorting will cause the request to fail.

We don't have any UIs that allow the user to create an index, except for Console.

[mattkime]

@stacey-gammon Do you know when the runtime fields will be available vis the field_caps api? I'm unable to tell if its an additional step or if its indirectly implied by other work.

update - found the answer in a google doc. field caps support will be provided along with mapping support.

[TinaHeiligers]

@stacey-gammon The issue was missing labels. I added Meta. Should I add the teams to?
Thanks!

[stacey-gammon]

Closing in favor of https://github.com/elastic/kibana-team/issues/250