stack es get-source 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 get-source --id <id> --index <index> [options]
Get a document's source.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--idstringrequired- A unique document identifier.
--indexstringrequired- The name of the index that contains the document.
--preferencestring- The node or shard the operation should be performed on. By default, the operation is randomized between the shard replicas.
--realtime- If
true, the request is real-time as opposed to near-real-time. --refresh- If
true, the request refreshes the relevant shards before retrieving the document. Setting it totrueshould be done after careful thought and verification that this does not cause a heavy load on the system (and slow down indexing). --routingstring-
A custom value used to route operations to a specific shard.
Repeatable: pass
--routingmultiple times to supply more than one value --sourcestring- Indicates whether to return the
_sourcefield (trueorfalse) or lists the fields to return. --source-excludesstring-
A comma-separated list of source fields to exclude in the response.
Repeatable: pass
--source-excludesmultiple times to supply more than one value --source-includesstring-
A comma-separated list of source fields to include in the response.
Repeatable: pass
--source-includesmultiple times to supply more than one value --versionnumber- The version number for concurrency control. It must match the current version of the document for the request to succeed.
--version-typeenum-
The version type.
Values: internal, external, external_gte
--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