stack es open-point-in-time cli command
elastic stack es open-point-in-time \
--index <index> \
--keep-alive <keep-alive> \
[options]
Open a point in time.
--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 --keep-alivestringrequired- Extend the length of time that the point in time persists.
- 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-wildcardsstring-
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.Repeatable: pass
--expand-wildcardsmultiple times to supply more than one value --[no-]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.
--input-filestring- path to a JSON file to use as command input
-V--[no-]version- Print the Elastic CLI version
--config-filestring- path to a config file (default: ~/.elasticrc.yml)
--use-contextstring- override the active context from the config file
--command-profilestring- restrict available commands to a deployment profile (serverless, stack, default)
--[no-]json- output as JSON
--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}}")
--[no-]dry-run-
validate all inputs and exit without performing any action (preview changes without applying them)