-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS] Clarify indexing a runtime field #77117
[DOCS] Clarify indexing a runtime field #77117
Conversation
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-search (Team:Search) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick turnaround @lockewritesdocs! Lgtm, but I'd be more at ease if more knowledgeable colleagues like @javanna or @romseygeek would have a quick look too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'd say 'uses these indexed fields to drive queries', rather than saying it uses them first; but other than that, LGTM.
💔 Backport failed
To backport manually run |
* [DOCS] Clarify indexing a runtime field * Clarify wording based on reviewer feedback # Conflicts: # docs/reference/mapping/runtime.asciidoc
* [DOCS] Clarify indexing a runtime field * Clarify wording based on reviewer feedback # Conflicts: # docs/reference/mapping/runtime.asciidoc
Borrows some language from the Compromises section for runtime fields to expand the explanation around indexing a runtime field.
Preview link: https://elasticsearch_77117.docs-preview.app.elstc.co/guide/en/elasticsearch/reference/master/runtime-indexed.html
Closes #77102