stack es create cli command

elastic stack es create \
  --id <id> \
  --index <index> \
  --document <document> \
  [options]
		

Create a new document in the index.

Behaviour flags:

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

--id string required

A unique identifier for the document. To automatically generate a document ID, use the POST /<target>/_doc/ request format.

--index string required

The name of the data stream or index to target. If the target doesn't exist and matches the name or wildcard (*) pattern of an index template with a data_stream definition, this request creates the data stream. If the target doesn't exist and doesn’t match a data stream template, this request creates the index.

--document string required

--[no-]include-source-on-error

True or false if to include the document source in the error message in case of parsing errors.

--pipeline string

The ID of the pipeline to use to preprocess incoming documents. If the index has a default ingest pipeline specified, setting the value to _none turns off the default ingest pipeline for this request. If a final pipeline is configured, it will always run regardless of the value of this parameter.

--[no-]refresh

If true, Elasticsearch refreshes the affected shards to make this operation visible to search. If wait_for, it waits for a refresh to make this operation visible to search. If false, it does nothing with refreshes.

--[no-]require-alias

If true, the destination must be an index alias.

--[no-]require-data-stream

If true, the request's actions must target a data stream (existing or to be created).

--routing string

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

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

--timeout string

The period the request waits for the following operations: automatic index creation, dynamic mapping updates, waiting for active shards. Elasticsearch waits for at least the specified timeout period before failing. The actual wait time could be longer, particularly when multiple waits occur. This parameter is useful for situations where the primary shard assigned to perform the operation might not be available when the operation runs. Some reasons for this might be that the primary shard is currently recovering from a gateway or undergoing relocation. By default, the operation will wait on the primary shard to become available for at least 1 minute before failing and responding with an error. The actual wait time could be longer, particularly when multiple waits occur.

--version number

The explicit version number for concurrency control. It must be a non-negative long number.

--version-type string

The version type.

--wait-for-active-shards number

The number of shard copies that must be active before proceeding with the operation. You can set it to all or any positive integer up to the total number of shards in the index (number_of_replicas+1). The default value of 1 means it waits for each primary shard to be active.

--input-file string

path to a JSON file to use as command input

--[no-]dry-run

validate all inputs and exit without performing any action (preview changes without applying them)

--[no-]json

output as JSON