Overview

This PR proposes changes on top of

• [RFC 0050] Stage 2: Introducing GenAI fields #2475

based on discussion with @felixbarny @eyalkoren in this PR:

• Update ecs@mappings.json with new GenAI fields elasticsearch#129122

namely, updating gen_ai.request.model and gen_ai.agent.description from text to keyword.

The rationale:

• gen_ai.request.model: doesn't require text analyzing
• gen_ai.agent.description: phrase queries may not be used often for this field, and may be expensive from storage and indexing - via @felixbarny

While it has a limit on how many characters it can store in doc_values it falls back to storing the value in a stored field if ignore_above is set, which seems like a good compromise here.

I'm looking for feedback if this is covered, as it's part of the generated files and I'm not completely sure which changes are expected for ignore_above to work.

Checklist

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?
• For proposing substantial changes or additions to the schema, have you reviewed the RFC process?
• If submitting code/script changes, have you verified all tests pass locally using make test?
• If submitting schema/fields updates, have you generated new artifacts by running make and committed those changes?
• Is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
• Have you added an entry to the CHANGELOG.next.md?