[DOCS] Fix double spaces (#71082)

This commit is contained in:
James Rodewig 2021-03-31 09:57:47 -04:00 committed by GitHub
parent 83725e4b38
commit 693807a6d3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
282 changed files with 834 additions and 834 deletions

View file

@ -121,7 +121,7 @@ It cannot return JSON objects.
The `doc['field']` will throw an error if `field` is missing from the mappings.
In `painless`, a check can first be done with `doc.containsKey('field')` to guard
accessing the `doc` map. Unfortunately, there is no way to check for the
accessing the `doc` map. Unfortunately, there is no way to check for the
existence of the field in mappings in an `expression` script.
===================================================
@ -133,7 +133,7 @@ existence of the field in mappings in an `expression` script.
The `doc['field']` syntax can also be used for <<text,analyzed `text` fields>>
if <<fielddata,`fielddata`>> is enabled, but *BEWARE*: enabling fielddata on a
`text` field requires loading all of the terms into the JVM heap, which can be
very expensive both in terms of memory and CPU. It seldom makes sense to
very expensive both in terms of memory and CPU. It seldom makes sense to
access `text` fields from scripts.
===================================================
@ -250,7 +250,7 @@ GET my-index-000001/_search
=======================================================
The `_source` field is just a special stored field, so the performance is
similar to that of other stored fields. The `_source` provides access to the
similar to that of other stored fields. The `_source` provides access to the
original document body that was indexed (including the ability to distinguish
`null` values from empty fields, single-value arrays from plain scalars, etc).

View file

@ -101,9 +101,9 @@ script.allowed_types: inline <1>
[discrete]
=== Allowed script contexts setting
By default all script contexts are allowed to be executed. This can be modified using the
setting `script.allowed_contexts`. Only the contexts specified as part of the setting will
be allowed to be executed. To specify no contexts are allowed, set `script.allowed_contexts`
By default all script contexts are allowed to be executed. This can be modified using the
setting `script.allowed_contexts`. Only the contexts specified as part of the setting will
be allowed to be executed. To specify no contexts are allowed, set `script.allowed_contexts`
to be `none`.
[source,yaml]