stack es termvectors 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 termvectors --index <index> [options]
Get term vector information.
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--indexstringrequired- The name of the index that contains the document.
--fieldsstring[]-
A list of fields to include in the statistics. It is used as the default list unless a specific field list is provided in the
completion_fieldsorfielddata_fieldsparameters.Repeatable: pass
--fieldsmultiple times to supply more than one value --field-statistics-
If
true, the response includes: * The document count (how many documents contain this field).- The sum of document frequencies (the sum of document frequencies for all terms in this field).
- The sum of total term frequencies (the sum of total term frequencies of each term in this field).
--offsets- If
true, the response includes term offsets. --payloads- If
true, the response includes term payloads. --positions- If
true, the response includes term positions. --preferencestring- The node or shard the operation should be performed on. It is random by default.
--realtime- If true, the request is real-time as opposed to near-real-time.
--routingstring-
A custom value that is used to route operations to a specific shard.
Repeatable: pass
--routingmultiple times to supply more than one value --term-statistics-
If
true, the response includes: * The total term frequency (how often a term occurs in all documents).- The document frequency (the number of documents containing the current term). By default these values are not returned since term statistics can have a serious performance impact.
--versionnumber- If
true, returns the document version as part of a hit. --version-typeenum-
The version type.
Values: internal, external, external_gte
--docstring- An artificial document (a document not present in the index) for which you want to retrieve term vectors.
--filterstring- Filter terms based on their tf-idf scores. This could be useful in order find out a good characteristic vector of a document. This feature works in a similar manner to the second phase of the More Like This Query.
--per-field-analyzerstring- Override the default per-field analyzer. This is useful in order to generate term vectors in any fashion, especially when using artificial documents. When providing an analyzer for a field that already stores term vectors, the term vectors will be regenerated.
--idstring- A unique identifier for the document.
--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