Skip to content

[7.x] [DOCS] Remove performance warning for script fields (#69309) #69354

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

Merged
merged 1 commit into from
Feb 22, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/reference/how-to/search-speed.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -165,8 +165,8 @@ include::../mapping/types/numeric.asciidoc[tag=map-ids-as-keyword]
[discrete]
=== Avoid scripts

If possible, avoid using <<modules-scripting,scripts>> or
<<script-fields,scripted fields>> in searches. See
If possible, avoid using <<modules-scripting,script>>-based sorting, scripts in
aggregations, and the <<query-dsl-script-score-query,`script_score`>> query. See
<<scripts-and-search-speed>>.


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -43,10 +43,8 @@ such as keywords and dates.
get the values for specific stored fields (fields that use the
<<mapping-store,`store`>> mapping option).

If needed, you can use the <<script-fields,`script_field`>> parameter to
transform field values in the response using a script. However, scripts can’t
make use of {es}'s index structures or related optimizations. This can sometimes
result in slower search speeds.
You can also use the <<script-fields,`script_field`>> parameter to transform
field values in the response using a script.

You can find more detailed information on each of these methods in the
following sections:
Expand Down