Class ElasticsearchDanglingIndicesAsyncClient
- All Implemented Interfaces:
Closeable
,AutoCloseable
-
Field Summary
Fields inherited from class co.elastic.clients.ApiClient
transport, transportOptions
-
Constructor Summary
ConstructorsConstructorDescriptionElasticsearchDanglingIndicesAsyncClient
(ElasticsearchTransport transport, TransportOptions transportOptions) -
Method Summary
Modifier and TypeMethodDescriptionDelete a dangling index.deleteDanglingIndex
(Function<DeleteDanglingIndexRequest.Builder, ObjectBuilder<DeleteDanglingIndexRequest>> fn) Delete a dangling index.Import a dangling index.importDanglingIndex
(Function<ImportDanglingIndexRequest.Builder, ObjectBuilder<ImportDanglingIndexRequest>> fn) Import a dangling index.Get the dangling indices.withTransportOptions
(TransportOptions transportOptions) Creates a new client with some request optionsMethods inherited from class co.elastic.clients.ApiClient
_jsonpMapper, _transport, _transportOptions, close, getDeserializer, withTransportOptions
-
Constructor Details
-
ElasticsearchDanglingIndicesAsyncClient
-
ElasticsearchDanglingIndicesAsyncClient
public ElasticsearchDanglingIndicesAsyncClient(ElasticsearchTransport transport, @Nullable TransportOptions transportOptions)
-
-
Method Details
-
withTransportOptions
public ElasticsearchDanglingIndicesAsyncClient withTransportOptions(@Nullable TransportOptions transportOptions) Description copied from class:ApiClient
Creates a new client with some request options- Specified by:
withTransportOptions
in classApiClient<ElasticsearchTransport,
ElasticsearchDanglingIndicesAsyncClient>
-
deleteDanglingIndex
public CompletableFuture<DeleteDanglingIndexResponse> deleteDanglingIndex(DeleteDanglingIndexRequest request) Delete a dangling index. If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling. For example, this can happen if you delete more thancluster.indices.tombstones.size
indices while an Elasticsearch node is offline.- See Also:
-
deleteDanglingIndex
public final CompletableFuture<DeleteDanglingIndexResponse> deleteDanglingIndex(Function<DeleteDanglingIndexRequest.Builder, ObjectBuilder<DeleteDanglingIndexRequest>> fn) Delete a dangling index. If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling. For example, this can happen if you delete more thancluster.indices.tombstones.size
indices while an Elasticsearch node is offline.- Parameters:
fn
- a function that initializes a builder to create theDeleteDanglingIndexRequest
- See Also:
-
importDanglingIndex
public CompletableFuture<ImportDanglingIndexResponse> importDanglingIndex(ImportDanglingIndexRequest request) Import a dangling index.If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling. For example, this can happen if you delete more than
cluster.indices.tombstones.size
indices while an Elasticsearch node is offline.- See Also:
-
importDanglingIndex
public final CompletableFuture<ImportDanglingIndexResponse> importDanglingIndex(Function<ImportDanglingIndexRequest.Builder, ObjectBuilder<ImportDanglingIndexRequest>> fn) Import a dangling index.If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling. For example, this can happen if you delete more than
cluster.indices.tombstones.size
indices while an Elasticsearch node is offline.- Parameters:
fn
- a function that initializes a builder to create theImportDanglingIndexRequest
- See Also:
-
listDanglingIndices
Get the dangling indices.If Elasticsearch encounters index data that is absent from the current cluster state, those indices are considered to be dangling. For example, this can happen if you delete more than
cluster.indices.tombstones.size
indices while an Elasticsearch node is offline.Use this API to list dangling indices, which you can then import or delete.
- See Also:
-