stack es open-point-in-time cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic stack es open-point-in-time \
--keep-alive <keep-alive> \
--index <index> \
[options]
Open a point in time.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--keep-alivestringrequired- Extend the length of time that the point in time persists.
--indexstringrequired-
A comma-separated list of index names to open point in time; use
_allor empty string to perform the operation on all indicesRepeatable: pass
--indexmultiple times to supply more than one value - If
false, the request returns an error if it targets a concrete (non-wildcarded) index, alias, or data stream that is missing, closed, or otherwise unavailable. Iftrue, unavailable concrete targets are silently ignored. --preferencestring- The node or shard the operation should be performed on. By default, it is random.
--routingstring-
A custom value that is used to route operations to a specific shard.
Repeatable: pass
--routingmultiple times to supply more than one value --expand-wildcardsenum-
The type of index that wildcard patterns can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. It supports comma-separated values, such as
open,hidden.Values: all, open, closed, hidden, none
Repeatable: pass
--expand-wildcardsmultiple times to supply more than one value --allow-partial-search-results- Indicates whether the point in time tolerates unavailable shards or shard failures when initially creating the PIT.
If
false, creating a point in time request when a shard is missing or unavailable will throw an exception. Iftrue, the point in time will contain all the shards that are available at the time of the request. --max-concurrent-shard-requestsnumber- Maximum number of concurrent shard requests that each sub-search request executes per node.
--index-filterstring- Filter indices if the provided query rewrites to
match_noneon every shard. --error-trace- When set to
trueElasticsearch will include the full stack trace of errors when they occur. --filter-pathstring-
Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch.
Repeatable: pass
--filter-pathmultiple times to supply more than one value --human- When set to
truewill return statistics in a format suitable for humans. For example"exists_time": "1h"for humans and"exists_time_in_millis": 3600000for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines. --pretty- If set to
truethe returned JSON will be "pretty-formatted". Only use this option for debugging only. --input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON