diff --git a/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchAsyncClient.java b/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchAsyncClient.java
index 2c8fac0c11..99c67a9a05 100644
--- a/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchAsyncClient.java
+++ b/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchAsyncClient.java
@@ -116,6 +116,7 @@
import co.elastic.clients.elasticsearch.core.UpdateRequest;
import co.elastic.clients.elasticsearch.core.UpdateResponse;
import co.elastic.clients.elasticsearch.dangling_indices.ElasticsearchDanglingIndicesAsyncClient;
+import co.elastic.clients.elasticsearch.encryption.ElasticsearchEncryptionAsyncClient;
import co.elastic.clients.elasticsearch.enrich.ElasticsearchEnrichAsyncClient;
import co.elastic.clients.elasticsearch.eql.ElasticsearchEqlAsyncClient;
import co.elastic.clients.elasticsearch.esql.ElasticsearchEsqlAsyncClient;
@@ -246,6 +247,10 @@ public ElasticsearchDanglingIndicesAsyncClient danglingIndices() {
return new ElasticsearchDanglingIndicesAsyncClient(this.transport, this.transportOptions);
}
+ public ElasticsearchEncryptionAsyncClient encryption() {
+ return new ElasticsearchEncryptionAsyncClient(this.transport, this.transportOptions);
+ }
+
public ElasticsearchEnrichAsyncClient enrich() {
return new ElasticsearchEnrichAsyncClient(this.transport, this.transportOptions);
}
@@ -537,12 +542,6 @@ public ElasticsearchXpackAsyncClient xpack() {
* NOTE: Data streams do not support custom routing unless they were created
* with the allow_custom_routing setting enabled in the template.
*
- * Wait for active shards - *
- * When making bulk calls, you can set the wait_for_active_shards
- * parameter to require a minimum number of shard copies to be active before
- * starting to process the bulk request.
- *
* Refresh *
* Control when the changes made by this request are visible to search.
@@ -719,12 +718,6 @@ public CompletableFuture
- * Wait for active shards
- *
- * When making bulk calls, you can set the
* Refresh
*
* Control when the changes made by this request are visible to search.
@@ -901,12 +894,6 @@ public final CompletableFuture
- * Wait for active shards
- *
- * When making bulk calls, you can set the
* Refresh
*
* Control when the changes made by this request are visible to search.
@@ -3151,7 +3138,8 @@ public CompletableFuture
* NOTE: Replica shards might not all be started when an indexing operation
* returns successfully. By default, only the primary is required. Set
- *
* Automatically create data streams and indices
*
@@ -3227,7 +3215,8 @@ public CompletableFuture
* Valid values are all or any positive integer up to the total number of
* configured copies per shard in the index (which is
@@ -3360,7 +3349,8 @@ public
* Automatically create data streams and indices
*
@@ -3436,7 +3426,8 @@ public
* Valid values are all or any positive integer up to the total number of
* configured copies per shard in the index (which is
@@ -6559,19 +6550,6 @@ public final
- * Waiting for active shards
- *
- *
* Throttling update requests
*
* To control the rate at which update by query issues batches of update
@@ -6721,19 +6699,6 @@ public CompletableFuture
- * Waiting for active shards
- *
- *
* Throttling update requests
*
* To control the rate at which update by query issues batches of update
diff --git a/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchClient.java b/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchClient.java
index 0b6ee66feb..9a85b7554b 100644
--- a/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchClient.java
+++ b/java-client/src/main/java/co/elastic/clients/elasticsearch/ElasticsearchClient.java
@@ -117,6 +117,7 @@
import co.elastic.clients.elasticsearch.core.UpdateRequest;
import co.elastic.clients.elasticsearch.core.UpdateResponse;
import co.elastic.clients.elasticsearch.dangling_indices.ElasticsearchDanglingIndicesClient;
+import co.elastic.clients.elasticsearch.encryption.ElasticsearchEncryptionClient;
import co.elastic.clients.elasticsearch.enrich.ElasticsearchEnrichClient;
import co.elastic.clients.elasticsearch.eql.ElasticsearchEqlClient;
import co.elastic.clients.elasticsearch.esql.ElasticsearchEsqlClient;
@@ -246,6 +247,10 @@ public ElasticsearchDanglingIndicesClient danglingIndices() {
return new ElasticsearchDanglingIndicesClient(this.transport, this.transportOptions);
}
+ public ElasticsearchEncryptionClient encryption() {
+ return new ElasticsearchEncryptionClient(this.transport, this.transportOptions);
+ }
+
public ElasticsearchEnrichClient enrich() {
return new ElasticsearchEnrichClient(this.transport, this.transportOptions);
}
@@ -537,12 +542,6 @@ public ElasticsearchXpackClient xpack() {
* NOTE: Data streams do not support custom routing unless they were created
* with the
- * Wait for active shards
- *
- * When making bulk calls, you can set the
* Refresh
*
* Control when the changes made by this request are visible to search.
@@ -719,12 +718,6 @@ public BulkResponse bulk(BulkRequest request) throws IOException, ElasticsearchE
* NOTE: Data streams do not support custom routing unless they were created
* with the
- * Wait for active shards
- *
- * When making bulk calls, you can set the
* Refresh
*
* Control when the changes made by this request are visible to search.
@@ -902,12 +895,6 @@ public final BulkResponse bulk(Function
- * Wait for active shards
- *
- * When making bulk calls, you can set the
* Refresh
*
* Control when the changes made by this request are visible to search.
@@ -3172,7 +3159,8 @@ public HealthReportResponse healthReport() throws IOException, ElasticsearchExce
*
* NOTE: Replica shards might not all be started when an indexing operation
* returns successfully. By default, only the primary is required. Set
- *
* Automatically create data streams and indices
*
@@ -3248,7 +3236,8 @@ public HealthReportResponse healthReport() throws IOException, ElasticsearchExce
*
* Valid values are all or any positive integer up to the total number of
* configured copies per shard in the index (which is
@@ -3381,7 +3370,8 @@ public
* NOTE: Replica shards might not all be started when an indexing operation
* returns successfully. By default, only the primary is required. Set
- *
* Automatically create data streams and indices
*
@@ -3457,7 +3447,8 @@ public
* Valid values are all or any positive integer up to the total number of
* configured copies per shard in the index (which is
@@ -6611,19 +6602,6 @@ public final
- * Waiting for active shards
- *
- *
* Throttling update requests
*
* To control the rate at which update by query issues batches of update
@@ -6774,19 +6752,6 @@ public UpdateByQueryResponse updateByQuery(UpdateByQueryRequest request)
* you can use to cancel or get the status of the task. Elasticsearch creates a
* record of this task as a document at
- * Waiting for active shards
- *
- *
* Throttling update requests
*
* To control the rate at which update by query issues batches of update
diff --git a/java-client/src/main/java/co/elastic/clients/elasticsearch/_types/FlushStats.java b/java-client/src/main/java/co/elastic/clients/elasticsearch/_types/FlushStats.java
index 6eb63872d1..6e75539fb3 100644
--- a/java-client/src/main/java/co/elastic/clients/elasticsearch/_types/FlushStats.java
+++ b/java-client/src/main/java/co/elastic/clients/elasticsearch/_types/FlushStats.java
@@ -68,6 +68,11 @@ public class FlushStats implements JsonpSerializable {
private final long totalTimeInMillis;
+ @Nullable
+ private final Time totalTimeExcludingWaiting;
+
+ private final long totalTimeExcludingWaitingOnLockInMillis;
+
// ---------------------------------------------------------------------------------------------
private FlushStats(Builder builder) {
@@ -76,6 +81,9 @@ private FlushStats(Builder builder) {
this.total = ApiTypeHelper.requireNonNull(builder.total, this, "total", 0);
this.totalTime = builder.totalTime;
this.totalTimeInMillis = ApiTypeHelper.requireNonNull(builder.totalTimeInMillis, this, "totalTimeInMillis", 0);
+ this.totalTimeExcludingWaiting = builder.totalTimeExcludingWaiting;
+ this.totalTimeExcludingWaitingOnLockInMillis = ApiTypeHelper.requireNonNull(
+ builder.totalTimeExcludingWaitingOnLockInMillis, this, "totalTimeExcludingWaitingOnLockInMillis", 0);
}
@@ -112,6 +120,21 @@ public final long totalTimeInMillis() {
return this.totalTimeInMillis;
}
+ /**
+ * API name: {@code total_time_excluding_waiting}
+ */
+ @Nullable
+ public final Time totalTimeExcludingWaiting() {
+ return this.totalTimeExcludingWaiting;
+ }
+
+ /**
+ * Required - API name: {@code total_time_excluding_waiting_on_lock_in_millis}
+ */
+ public final long totalTimeExcludingWaitingOnLockInMillis() {
+ return this.totalTimeExcludingWaitingOnLockInMillis;
+ }
+
/**
* Serialize this object to JSON.
*/
@@ -137,6 +160,14 @@ protected void serializeInternal(JsonGenerator generator, JsonpMapper mapper) {
generator.writeKey("total_time_in_millis");
generator.write(this.totalTimeInMillis);
+ if (this.totalTimeExcludingWaiting != null) {
+ generator.writeKey("total_time_excluding_waiting");
+ this.totalTimeExcludingWaiting.serialize(generator, mapper);
+
+ }
+ generator.writeKey("total_time_excluding_waiting_on_lock_in_millis");
+ generator.write(this.totalTimeExcludingWaitingOnLockInMillis);
+
}
@Override
@@ -160,6 +191,11 @@ public static class Builder extends WithJsonObjectBuilderBase
@@ -643,6 +668,8 @@ protected static void setupIndexingStatsDeserializer(ObjectDeserializerallow_custom_routing setting enabled in the template.
* wait_for_active_shards
- * parameter to require a minimum number of shard copies to be active before
- * starting to process the bulk request.
- * wait_for_active_shards
- * parameter to require a minimum number of shard copies to be active before
- * starting to process the bulk request.
- * wait_for_active_shards to change this default behavior.
+ * wait_for_active_shards to change this default behavior (this
+ * parameter is not available in Elasticsearch Serverless).
* 1). This default can be overridden in the index settings
* dynamically by setting index.write.wait_for_active_shards. To
* alter this behavior per operation, use the
- * wait_for_active_shards request parameter.
+ * wait_for_active_shards request parameter (this parameter is not
+ * available in Elasticsearch Serverless).
* wait_for_active_shards to change this default behavior.
+ * wait_for_active_shards to change this default behavior (this
+ * parameter is not available in Elasticsearch Serverless).
* index.write.wait_for_active_shards. To
* alter this behavior per operation, use the
- * wait_for_active_shards request parameter.
+ * wait_for_active_shards request parameter (this parameter is not
+ * available in Elasticsearch Serverless).
* wait_for_active_shards controls how many copies of a shard must
- * be active before proceeding with the request. See wait_for_active_shards
- * for details. timeout controls how long each write request waits
- * for unavailable shards to become available. Both work exactly the way they
- * work in the Bulk
- * API. Update by query uses scrolled searches, so you can also specify the
- * scroll parameter to control how long it keeps the search context
- * alive, for example ?scroll=10m. The default is 5 minutes.
- * .tasks/task/${taskId}.
* wait_for_active_shards controls how many copies of a shard must
- * be active before proceeding with the request. See wait_for_active_shards
- * for details. timeout controls how long each write request waits
- * for unavailable shards to become available. Both work exactly the way they
- * work in the Bulk
- * API. Update by query uses scrolled searches, so you can also specify the
- * scroll parameter to control how long it keeps the search context
- * alive, for example ?scroll=10m. The default is 5 minutes.
- * allow_custom_routing setting enabled in the template.
* wait_for_active_shards
- * parameter to require a minimum number of shard copies to be active before
- * starting to process the bulk request.
- * allow_custom_routing setting enabled in the template.
* wait_for_active_shards
- * parameter to require a minimum number of shard copies to be active before
- * starting to process the bulk request.
- * wait_for_active_shards
- * parameter to require a minimum number of shard copies to be active before
- * starting to process the bulk request.
- * wait_for_active_shards to change this default behavior.
+ * wait_for_active_shards to change this default behavior (this
+ * parameter is not available in Elasticsearch Serverless).
* 1). This default can be overridden in the index settings
* dynamically by setting index.write.wait_for_active_shards. To
* alter this behavior per operation, use the
- * wait_for_active_shards request parameter.
+ * wait_for_active_shards request parameter (this parameter is not
+ * available in Elasticsearch Serverless).
* wait_for_active_shards to change this default behavior.
+ * wait_for_active_shards to change this default behavior (this
+ * parameter is not available in Elasticsearch Serverless).
* 1). This default can be overridden in the index settings
* dynamically by setting index.write.wait_for_active_shards. To
* alter this behavior per operation, use the
- * wait_for_active_shards request parameter.
+ * wait_for_active_shards request parameter (this parameter is not
+ * available in Elasticsearch Serverless).
* .tasks/task/${taskId}.
* wait_for_active_shards controls how many copies of a shard must
- * be active before proceeding with the request. See wait_for_active_shards
- * for details. timeout controls how long each write request waits
- * for unavailable shards to become available. Both work exactly the way they
- * work in the Bulk
- * API. Update by query uses scrolled searches, so you can also specify the
- * scroll parameter to control how long it keeps the search context
- * alive, for example ?scroll=10m. The default is 5 minutes.
- * .tasks/task/${taskId}.
* wait_for_active_shards controls how many copies of a shard must
- * be active before proceeding with the request. See wait_for_active_shards
- * for details. timeout controls how long each write request waits
- * for unavailable shards to become available. Both work exactly the way they
- * work in the Bulk
- * API. Update by query uses scrolled searches, so you can also specify the
- * scroll parameter to control how long it keeps the search context
- * alive, for example ?scroll=10m. The default is 5 minutes.
- *