This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
Delete the lifecycle of a data stream
editDelete the lifecycle of a data stream
editDeletes the lifecycle from a set of data streams.
Prerequisites
edit-
If the Elasticsearch security features are enabled, you must have the
manage_data_stream_lifecycleindex privilege or higher to use this API. For more information, see Security privileges.
Request
editDELETE _data_stream/<data-stream>/_lifecycle
Description
editDeletes the lifecycle from the specified data streams. If multiple data streams are provided but at least one of them
does not exist, then the deletion of the lifecycle will fail for all of them and the API will respond with 404.
Path parameters
edit-
<data-stream> -
(Required, string) Comma-separated list of data streams used to limit the request. Supports wildcards (
*). To target all data streams use*or_all.
Query parameters
edit-
expand_wildcards -
(Optional, string) Type of data stream that wildcard patterns can match. Supports comma-separated values, such as
open,hidden. Valid values are:-
all,hidden - Match any data stream, including hidden ones.
-
open,closed - Matches any non-hidden data stream. Data streams cannot be closed.
-
none - Wildcard patterns are not accepted.
Defaults to
open. -
Examples
editThe following example deletes the lifecycle of my-data-stream:
resp = client.indices.delete_data_lifecycle(
name="my-data-stream",
)
print(resp)
response = client.indices.delete_data_lifecycle( name: 'my-data-stream' ) puts response
const response = await client.indices.deleteDataLifecycle({
name: "my-data-stream",
});
console.log(response);
DELETE _data_stream/my-data-stream/_lifecycle
When the policy is successfully deleted from all selected data streams, you receive the following result:
{
"acknowledged": true
}