Class ImportDanglingIndexRequest

java.lang.Object
co.elastic.clients.elasticsearch._types.RequestBase
co.elastic.clients.elasticsearch.dangling_indices.ImportDanglingIndexRequest

public class ImportDanglingIndexRequest extends RequestBase
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:
  • Field Details

  • Method Details

    • of

    • acceptDataLoss

      public final boolean acceptDataLoss()
      Required - This parameter must be set to true to import a dangling index. Because Elasticsearch cannot know where the dangling index data came from or determine which shard copies are fresh and which are stale, it cannot guarantee that the imported data represents the latest state of the index when it was last in the cluster.

      API name: accept_data_loss

    • indexUuid

      public final String indexUuid()
      Required - The UUID of the index to import. Use the get dangling indices API to locate the UUID.

      API name: index_uuid

    • masterTimeout

      @Nullable public final Time masterTimeout()
      Specify timeout for connection to master

      API name: master_timeout

    • timeout

      @Nullable public final Time timeout()
      Explicit operation timeout

      API name: timeout