Class ElasticsearchDanglingIndicesAsyncClient
- All Implemented Interfaces:
- Closeable,- AutoCloseable
- 
Field SummaryFields inherited from class co.elastic.clients.ApiClienttransport, transportOptions
- 
Constructor SummaryConstructorsConstructorDescriptionElasticsearchDanglingIndicesAsyncClient(ElasticsearchTransport transport, TransportOptions transportOptions) 
- 
Method SummaryModifier 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
- 
ElasticsearchDanglingIndicesAsyncClientpublic ElasticsearchDanglingIndicesAsyncClient(ElasticsearchTransport transport, @Nullable TransportOptions transportOptions) 
 
- 
- 
Method Details- 
withTransportOptionspublic ElasticsearchDanglingIndicesAsyncClient withTransportOptions(@Nullable TransportOptions transportOptions) Description copied from class:ApiClientCreates a new client with some request options- Specified by:
- withTransportOptionsin class- ApiClient<ElasticsearchTransport,- ElasticsearchDanglingIndicesAsyncClient> 
 
- 
deleteDanglingIndexpublic 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.sizeindices while an Elasticsearch node is offline.- See Also:
 
- 
deleteDanglingIndexpublic 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.sizeindices while an Elasticsearch node is offline.- Parameters:
- fn- a function that initializes a builder to create the- DeleteDanglingIndexRequest
- See Also:
 
- 
importDanglingIndexpublic 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.sizeindices while an Elasticsearch node is offline.- See Also:
 
- 
importDanglingIndexpublic 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.sizeindices while an Elasticsearch node is offline.- Parameters:
- fn- a function that initializes a builder to create the- ImportDanglingIndexRequest
- See Also:
 
- 
listDanglingIndicesGet 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.sizeindices while an Elasticsearch node is offline.Use this API to list dangling indices, which you can then import or delete. - See Also:
 
 
-