[WIP] increase mapping field meta char limit #131634
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: I never put this through review, and am unsure if increasing the default here would cause any significant or nuanced issues.
I did this work with the intent to evaluate how much increased field-level meta (for descriptions) would help an LLM in picking which indices should be searched, given a natural language prompt. Unfortunately, it became clear quite quickly that this approach wouldn't scale. Even just sending 20 index mappings with no metadata was too much for the EIS LLM to process in a single message context.
Instead, I'm taking an approach outlined in elastic/kibana#232437, to attempt to improve our index selection via top-level descriptions and/or a flat listing of field names.
We may revisit this topic, but it's probably important first to explore making index metadata searchable, before worrying about expanding how much index metadata we can even set.
to use this PR
./gradlew localDistro