Type to search.

stack es exists-source cli command

Serverless Preview

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Preview

    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.

Stack Preview

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Preview

    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.

Auth required Idempotent Scope: global
Shell
elastic stack es exists-source --id <id> --index <index> [options]

Check for a document source.

Behaviour flags:

--dry-run — validate all inputs and exit without performing any action

--id string required
A unique identifier for the document.
--index string required
A comma-separated list of data streams, indices, and aliases. It supports wildcards (*).
--preference string
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 to true should be done after careful thought and verification that this does not cause a heavy load on the system (and slow down indexing).
--routing string

A custom value used to route operations to a specific shard.

Repeatable: pass --routing multiple times to supply more than one value

--source string
Indicates whether to return the _source field (true or false) or lists the fields to return.
--source-excludes string

A comma-separated list of source fields to exclude in the response.

Repeatable: pass --source-excludes multiple times to supply more than one value

--source-includes string

A comma-separated list of source fields to include in the response.

Repeatable: pass --source-includes multiple times to supply more than one value

--version number
The version number for concurrency control. It must match the current version of the document for the request to succeed.
--version-type enum

The version type.

Values: internal, external, external_gte

--error-trace
When set to true Elasticsearch will include the full stack trace of errors when they occur.
--filter-path string

Comma-separated list of filters in dot notation which reduce the response returned by Elasticsearch.

Repeatable: pass --filter-path multiple times to supply more than one value

--human
When set to true will return statistics in a format suitable for humans. For example "exists_time": "1h" for humans and "exists_time_in_millis": 3600000 for computers. When disabled the human readable values will be omitted. This makes sense for responses being consumed only by machines.
--pretty
If set to true the returned JSON will be "pretty-formatted". Only use this option for debugging only.
--input-file string
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-fields string
comma-separated list of fields to include in output (dot-notation supported)
--output-template string
Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json

output as JSON