The OpenSearch dangling index APIs — every endpoint tagged Dangling Indices in the OpenSearch OpenAPI specification.

Built on Dowser.Client. Required OpenSearch attributes are positional arguments; everything optional lives in opts.

An index becomes dangling when its directory is present on a node but the cluster metadata knows nothing about it — a node rejoining after the index was deleted while it was away, or data restored underneath a fresh cluster. Such an index is inert: it is neither searchable nor writable until it is imported.

Both write endpoints are addressed by the index's UUID rather than its name, since a dangling index has no name the cluster agrees on. list/1 is where those UUIDs come from.

accept_data_loss

OpenSearch requires accept_data_loss=true on both writes, so it is a positional argument here rather than an option — there is no default that would be safe to assume:

• importing may resurrect an index whose deletion was deliberate, and whose shards may be missing or stale;
• deleting discards the data for good.

Passing false sends the parameter as given and lets OpenSearch reject it, rather than second-guessing the call here.

All remaining options are forwarded to Dowser.Client.request/4, e.g. :context, :params (query-string parameters), :format, :keys and :http_opts (including :headers) — plus :codec, this package's own, which picks the per-field codec for this one request (see Dowser.Opensearch.Codec).

On a 2xx response every function returns {:ok, body} with the decoded response body. A non-2xx response returns {:error, %Dowser.Opensearch.Error{}}; a transport, encoding or decoding failure returns {:error, exception} from Dowser.Client. A required argument that is missing or empty is reported the same way, before any request is made: {:error, %ArgumentError{}}. Each function has a bang variant that returns the body directly or raises the error exception.