mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 15:47:23 -04:00
Remove operationThreaded
from Java API (#27836)
This option is completely unused. Some places set it but we never read the value neither respect it.
This commit is contained in:
parent
c93cc1bb8f
commit
481d98b8d5
11 changed files with 9 additions and 95 deletions
|
@ -14,28 +14,6 @@ DeleteResponse response = client.prepareDelete("twitter", "tweet", "1").get();
|
|||
For more information on the delete operation, check out the
|
||||
{ref}/docs-delete.html[delete API] docs.
|
||||
|
||||
|
||||
[[java-docs-delete-thread]]
|
||||
==== Operation Threading
|
||||
|
||||
The delete API allows to set the threading model the operation will be
|
||||
performed when the actual execution of the API is performed on the same
|
||||
node (the API is executed on a shard that is allocated on the same
|
||||
server).
|
||||
|
||||
The options are to execute the operation on a different thread, or to
|
||||
execute it on the calling thread (note that the API is still async). By
|
||||
default, `operationThreaded` is set to `true` which means the operation
|
||||
is executed on a different thread. Here is an example that sets it to
|
||||
`false`:
|
||||
|
||||
[source,java]
|
||||
--------------------------------------------------
|
||||
DeleteResponse response = client.prepareDelete("twitter", "tweet", "1")
|
||||
.setOperationThreaded(false)
|
||||
.get();
|
||||
--------------------------------------------------
|
||||
|
||||
[[java-docs-delete-by-query]]
|
||||
=== Delete By Query API
|
||||
|
||||
|
|
|
@ -12,25 +12,3 @@ GetResponse response = client.prepareGet("twitter", "tweet", "1").get();
|
|||
|
||||
For more information on the get operation, check out the REST
|
||||
{ref}/docs-get.html[get] docs.
|
||||
|
||||
|
||||
[[java-docs-get-thread]]
|
||||
==== Operation Threading
|
||||
|
||||
The get API allows to set the threading model the operation will be
|
||||
performed when the actual execution of the API is performed on the same
|
||||
node (the API is executed on a shard that is allocated on the same
|
||||
server).
|
||||
|
||||
The options are to execute the operation on a different thread, or to
|
||||
execute it on the calling thread (note that the API is still async). By
|
||||
default, `operationThreaded` is set to `true` which means the operation
|
||||
is executed on a different thread. Here is an example that sets it to
|
||||
`false`:
|
||||
|
||||
[source,java]
|
||||
--------------------------------------------------
|
||||
GetResponse response = client.prepareGet("twitter", "tweet", "1")
|
||||
.setOperationThreaded(false)
|
||||
.get();
|
||||
--------------------------------------------------
|
||||
|
|
|
@ -163,16 +163,3 @@ RestStatus status = response.status();
|
|||
For more information on the index operation, check out the REST
|
||||
{ref}/docs-index_.html[index] docs.
|
||||
|
||||
|
||||
[[java-docs-index-thread]]
|
||||
==== Operation Threading
|
||||
|
||||
The index API allows one to set the threading model the operation will be
|
||||
performed when the actual execution of the API is performed on the same
|
||||
node (the API is executed on a shard that is allocated on the same
|
||||
server).
|
||||
|
||||
The options are to execute the operation on a different thread, or to
|
||||
execute it on the calling thread (note that the API is still asynchronous). By
|
||||
default, `operationThreaded` is set to `true` which means the operation
|
||||
is executed on a different thread.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue