Skip to content

Commit

Permalink
[DOCS] Word changes for runtime field incentives (#74769) (#74789)
Browse files Browse the repository at this point in the history
Incorporates feedback from #74454
  • Loading branch information
Adam Locke authored Jul 1, 2021
1 parent e1c6b52 commit 998a97f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/reference/mapping/runtime.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Runtime fields can replace many of the ways you can use scripting with the
documents that the included script runs against. For example, if you're using
the `fields` parameter on the `_search` API to
<<runtime-retrieving-fields,retrieve the values of a runtime field>>, the script
returns only the top hits just like script fields do.
runs only against the top hits just like script fields do.

You can use <<script-fields,script fields>> to access values in `_source` and
return calculated values based on a script valuation. Runtime fields have these
Expand All @@ -69,7 +69,7 @@ You can also use scripts to <<script-based-sorting,sort search results>>, but
that same script works exactly the same in a runtime field.

If you move a script from any of these sections in a search request to a
runtime field that is retrieving values from the same number of documents, the
runtime field that is computing values from the same number of documents, the
performance should be about the same. The performance for these features is
largely dependent upon the calculations that the included script is running and
how many documents the script runs against.
Expand Down

0 comments on commit 998a97f

Please sign in to comment.