mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-28 09:28:55 -04:00
[DOCS] Fix double spaces (#71082)
This commit is contained in:
James Rodewig
GitHub
parent
83725e4b38
commit
693807a6d3
282 changed files with 834 additions and 834 deletions
|
|
@ -51,7 +51,7 @@ offsets.
|
|||
payloads.
|
||||
<6> Set `filterSettings` to filter the terms that can be returned based
|
||||
on their tf-idf scores.
|
||||
<7> Set `perFieldAnalyzer` to specify a different analyzer than
|
||||
<7> Set `perFieldAnalyzer` to specify a different analyzer than
|
||||
the one that the field has.
|
||||
<8> Set `realtime` to `false` (default is `true`) to retrieve term vectors
|
||||
near realtime.
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ The simplest version uses a built-in analyzer:
|
|||
include-tagged::{doc-tests-file}[{api}-builtin-request]
|
||||
---------------------------------------------------
|
||||
<1> A built-in analyzer
|
||||
<2> The text to include. Multiple strings are treated as a multi-valued field
|
||||
<2> The text to include. Multiple strings are treated as a multi-valued field
|
||||
|
||||
You can configure a custom analyzer:
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
|
|||
--------------------------------------------------
|
||||
include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
|
||||
--------------------------------------------------
|
||||
<1> The number of active shard copies to wait for before the freeze index API
|
||||
<1> The number of active shard copies to wait for before the freeze index API
|
||||
returns a response, as an `ActiveShardCount`
|
||||
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ The following arguments can optionally be provided:
|
|||
--------------------------------------------------
|
||||
include-tagged::{doc-tests-file}[{api}-request-names]
|
||||
--------------------------------------------------
|
||||
<1> One or more settings that be the only settings retrieved. If unset, all settings will be retrieved
|
||||
<1> One or more settings that be the only settings retrieved. If unset, all settings will be retrieved
|
||||
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
--------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
|
|||
--------------------------------------------------
|
||||
<1> The number of active shard copies to wait for before the open index API
|
||||
returns a response, as an `int`
|
||||
<2> The number of active shard copies to wait for before the open index API
|
||||
<2> The number of active shard copies to wait for before the open index API
|
||||
returns a response, as an `ActiveShardCount`
|
||||
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ include-tagged::{doc-tests-file}[{api}-request-masterTimeout]
|
|||
--------------------------------------------------
|
||||
include-tagged::{doc-tests-file}[{api}-request-waitForActiveShards]
|
||||
--------------------------------------------------
|
||||
<1> The number of active shard copies to wait for before the unfreeze index API
|
||||
<1> The number of active shard copies to wait for before the unfreeze index API
|
||||
returns a response, as an `ActiveShardCount`
|
||||
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ license started. If it was not started, it returns an error message describing
|
|||
why.
|
||||
|
||||
Acknowledgement messages may also be returned if this API was called without
|
||||
the `acknowledge` flag set to `true`. In this case you need to display the
|
||||
the `acknowledge` flag set to `true`. In this case you need to display the
|
||||
messages to the end user and if they agree, resubmit the request with the
|
||||
`acknowledge` flag set to `true`. Please note that the response will still
|
||||
return a 200 return code even if it requires an acknowledgement. So, it is
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ license started. If it was not started, it returns an error message describing
|
|||
why.
|
||||
|
||||
Acknowledgement messages may also be returned if this API was called without
|
||||
the `acknowledge` flag set to `true`. In this case you need to display the
|
||||
the `acknowledge` flag set to `true`. In this case you need to display the
|
||||
messages to the end user and if they agree, resubmit the request with the
|
||||
`acknowledge` flag set to `true`. Please note that the response will still
|
||||
return a 200 return code even if it requires an acknowledgement. So, it is
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ include-tagged::{doc-tests-file}[x-pack-{api}-execute]
|
|||
|
||||
The returned +{response}+ holds lists and maps of values which correspond to the capabilities
|
||||
of the target index/index pattern (what jobs were configured for the pattern, where the data is stored, what
|
||||
aggregations are available, etc). It provides essentially the same data as the original job configuration,
|
||||
aggregations are available, etc). It provides essentially the same data as the original job configuration,
|
||||
just presented in a different manner.
|
||||
|
||||
For example, if we had created a job with the following config:
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@
|
|||
experimental::[]
|
||||
|
||||
The Get Rollup Index Capabilities API allows the user to determine if a concrete index or index pattern contains
|
||||
stored rollup jobs and data. If it contains data stored from rollup jobs, the capabilities of those jobs
|
||||
stored rollup jobs and data. If it contains data stored from rollup jobs, the capabilities of those jobs
|
||||
are returned. The API accepts a `GetRollupIndexCapsRequest` object as a request and returns a `GetRollupIndexCapsResponse`.
|
||||
|
||||
[id="{upid}-x-pack-{api}-request"]
|
||||
|
|
@ -40,7 +40,7 @@ include-tagged::{doc-tests-file}[x-pack-{api}-execute]
|
|||
|
||||
The returned +{response}+ holds lists and maps of values which correspond to the capabilities
|
||||
of the rollup index/index pattern (what jobs are stored in the index, their capabilities, what
|
||||
aggregations are available, etc). Because multiple jobs can be stored in one index, the
|
||||
aggregations are available, etc). Because multiple jobs can be stored in one index, the
|
||||
response may include several jobs with different configurations.
|
||||
|
||||
The capabilities are essentially the same as the original job configuration, just presented in a different
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ if the privilege was not part of the request).
|
|||
A `Map<String, Map<String, Map<String, Boolean>>>>` where each key is the
|
||||
name of an application (as specified in the +{request}+).
|
||||
For each application, the value is a `Map` keyed by resource name, with
|
||||
each value being another `Map` from privilege name to a `Boolean`.
|
||||
each value being another `Map` from privilege name to a `Boolean`.
|
||||
The `Boolean` value is `true` if the user has that privilege on that
|
||||
resource for that application, and `false` otherwise.
|
||||
+
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ include-tagged::{doc-tests}/SnapshotClientDocumentationIT.java[delete-snapshot-e
|
|||
[[java-rest-high-snapshot-delete-snapshot-async]]
|
||||
==== Asynchronous Execution
|
||||
|
||||
The asynchronous execution of a delete snapshot request requires both the
|
||||
The asynchronous execution of a delete snapshot request requires both the
|
||||
`DeleteSnapshotRequest` instance and an `ActionListener` instance to be
|
||||
passed to the asynchronous method:
|
||||
|
||||
|
|
|
|||
|
|
@ -150,7 +150,7 @@ should be consulted: https://hc.apache.org/httpcomponents-asyncclient-4.1.x/ .
|
|||
|
||||
NOTE: If your application runs under the security manager you might be subject
|
||||
to the JVM default policies of caching positive hostname resolutions
|
||||
indefinitely and negative hostname resolutions for ten seconds. If the resolved
|
||||
indefinitely and negative hostname resolutions for ten seconds. If the resolved
|
||||
addresses of the hosts to which you are connecting the client to vary with time
|
||||
then you might want to modify the default JVM behavior. These can be modified by
|
||||
adding
|
||||
|
|
@ -184,6 +184,6 @@ whenever none of the nodes from the preferred rack is available.
|
|||
|
||||
WARNING: Node selectors that do not consistently select the same set of nodes
|
||||
will make round-robin behaviour unpredictable and possibly unfair. The
|
||||
preference example above is fine as it reasons about availability of nodes
|
||||
preference example above is fine as it reasons about availability of nodes
|
||||
which already affects the predictability of round-robin. Node selection should
|
||||
not depend on other external factors or round-robin will not work properly.
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ include-tagged::{doc-tests}/SnifferDocumentation.java[sniff-on-failure]
|
|||
failure, but an additional sniffing round is also scheduled sooner than usual,
|
||||
by default one minute after the failure, assuming that things will go back to
|
||||
normal and we want to detect that as soon as possible. Said interval can be
|
||||
customized at `Sniffer` creation time through the `setSniffAfterFailureDelayMillis`
|
||||
customized at `Sniffer` creation time through the `setSniffAfterFailureDelayMillis`
|
||||
method. Note that this last configuration parameter has no effect in case sniffing
|
||||
on failure is not enabled like explained above.
|
||||
<3> Set the `Sniffer` instance to the failure listener
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue