mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
[DOCS] Various spelling corrections (#37046)
This commit is contained in:
parent
ac2e09b25a
commit
edb48321ba
66 changed files with 80 additions and 80 deletions
|
@ -128,7 +128,7 @@ include-tagged::{doc-tests-file}[{api}-conflict]
|
|||
--------------------------------------------------
|
||||
<1> `getResponse` is null.
|
||||
<2> `getFailure` isn't and contains an `Exception`.
|
||||
<3> That `Exception` is actuall and `ElasticsearchException`
|
||||
<3> That `Exception` is actually an `ElasticsearchException`
|
||||
<4> and it has a status of `CONFLICT`. It'd have been an HTTP 409 if this
|
||||
wasn't a multi get.
|
||||
<5> `getMessage` explains the actual cause, `
|
||||
|
|
|
@ -125,7 +125,7 @@ include::../execution.asciidoc[]
|
|||
[id="{upid}-{api}-response"]
|
||||
==== Update By Query Response
|
||||
|
||||
The returned +{resposne}+ contains information about the executed operations and
|
||||
The returned +{response}+ contains information about the executed operations and
|
||||
allows to iterate over each result as follows:
|
||||
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
|
|
|
@ -144,7 +144,7 @@ include-tagged::{doc-tests}/MiscellaneousDocumentationIT.java[rest-high-level-cl
|
|||
In the rest of this documentation about the Java High Level Client, the `RestHighLevelClient` instance
|
||||
will be referenced as `client`.
|
||||
|
||||
[[java-rest-hight-getting-started-request-options]]
|
||||
[[java-rest-high-getting-started-request-options]]
|
||||
=== RequestOptions
|
||||
|
||||
All APIs in the `RestHighLevelClient` accept a `RequestOptions` which you can
|
||||
|
|
|
@ -15,7 +15,7 @@ An +{request}+ requires an `index` argument:
|
|||
--------------------------------------------------
|
||||
include-tagged::{doc-tests-file}[{api}-request]
|
||||
--------------------------------------------------
|
||||
<1> The index to unreeze
|
||||
<1> The index to unfreeze
|
||||
|
||||
==== Optional arguments
|
||||
The following arguments can optionally be provided:
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
[[java-rest-high-migration-get-assistance]]
|
||||
=== Migration Get Assistance
|
||||
|
||||
[[java-rest-high-migraton-get-assistance-request]]
|
||||
[[java-rest-high-migration-get-assistance-request]]
|
||||
==== Index Upgrade Info Request
|
||||
|
||||
An `IndexUpgradeInfoRequest` does not require any argument:
|
||||
|
|
|
@ -8,7 +8,7 @@
|
|||
[[java-rest-high-migration-upgrade]]
|
||||
=== Migration Upgrade
|
||||
|
||||
[[java-rest-high-migraton-upgrade-request]]
|
||||
[[java-rest-high-migration-upgrade-request]]
|
||||
==== Index Upgrade Request
|
||||
|
||||
An +{request}+ requires an index argument. Only one index at the time should be upgraded:
|
||||
|
@ -32,7 +32,7 @@ include-tagged::{doc-tests-file}[{api}-execute]
|
|||
The returned +{response}+ contains information about the executed operation
|
||||
|
||||
|
||||
[[java-rest-high-migraton-async-upgrade-request]]
|
||||
[[java-rest-high-migration-async-upgrade-request]]
|
||||
==== Asynchronous Execution
|
||||
|
||||
The asynchronous execution of an upgrade request requires both the +{request}+
|
||||
|
|
|
@ -82,7 +82,7 @@ include-tagged::{doc-tests}/SearchDocumentationIT.java[rank-eval-response]
|
|||
<2> Partial results that are keyed by their query id
|
||||
<3> The metric score for each partial result
|
||||
<4> Rated search hits contain a fully fledged `SearchHit`
|
||||
<5> Rated search hits also contain an `Optional<Interger>` rating that
|
||||
<5> Rated search hits also contain an `Optional<Integer>` rating that
|
||||
is not present if the document did not get a rating in the request
|
||||
<6> Metric details are named after the metric used in the request
|
||||
<7> After casting to the metric used in the request, the
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
--
|
||||
:api: get-privileges
|
||||
:request: GetPrivilegesRequest
|
||||
:respnse: GetPrivilegesResponse
|
||||
:response: GetPrivilegesResponse
|
||||
--
|
||||
|
||||
[id="{upid}-{api}"]
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
--
|
||||
:api: get-roles
|
||||
:request: GetRolesRequest
|
||||
:respnse: GetRolesResponse
|
||||
:response: GetRolesResponse
|
||||
--
|
||||
|
||||
[id="{upid}-{api}"]
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
--
|
||||
:api: get-users
|
||||
:request: GetUsersRequest
|
||||
:respnse: GetUsersResponse
|
||||
:response: GetUsersResponse
|
||||
--
|
||||
|
||||
[id="{upid}-{api}"]
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
--
|
||||
:api: deactivate-watch
|
||||
:request: deactivateWatchRequet
|
||||
:request: deactivateWatchRequest
|
||||
:response: deactivateWatchResponse
|
||||
:doc-tests-file: {doc-tests}/WatcherDocumentationIT.java
|
||||
--
|
||||
|
|
|
@ -328,7 +328,7 @@ include-tagged::{doc-tests}/RestClientDocumentation.java[rest-client-options-cus
|
|||
|
||||
The client is quite happy to execute many actions in parallel. The following
|
||||
example indexes many documents in parallel. In a real world scenario you'd
|
||||
probably want to use the `_bulk` API instead, but the example is illustative.
|
||||
probably want to use the `_bulk` API instead, but the example is illustrative.
|
||||
|
||||
["source","java",subs="attributes,callouts,macros"]
|
||||
--------------------------------------------------
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue