Put an ElasticSearch document.
type: "io.kestra.plugin.elasticsearch.Put"
Put a document with a Map.
id: elasticsearch_put
namespace: company.team
tasks:
- id: put
type: io.kestra.plugin.elasticsearch.Put
connection:
hosts:
- "http://localhost:9200"
index: "my_index"
key: "my_id"
value:
name: "John Doe"
city: "Paris"
Put a document from a JSON string.
id: elasticsearch_put
namespace: company.team
inputs:
- id: value
type: JSON
defaults: {"name": "John Doe", "city": "Paris"}
tasks:
- id: put
type: io.kestra.plugin.elasticsearch.Put
connection:
hosts:
- "http://localhost:9200"
index: "my_index"
key: "my_id"
value: "{{ inputs.value }}"
NO
The connection properties.
YES
The elasticsearch index.
YES
JSON
CBOR
JSON
SMILE
YAML
The content type of value
.
YES
The elasticsearch id.
YES
INDEX
CREATE
UPDATE
DELETE
Sets the type of operation to perform.
YES
NONE
IMMEDIATE
WAIT_UNTIL
NONE
Should this request trigger a refresh.
an immediate refresh IMMEDIATE
, wait for a refresh WAIT_UNTIL
, or proceed ignore refreshes entirely NONE
.
YES
Controls the shard routing of the request.
Using this value to hash the shard and not the id.
YES
The elasticsearch value.
Can be a string. In this case, the contentType will be used or a raw Map.
The id of the document changed.
Created
Updated
Deleted
NotFound
NoOp
The change that occurred to the document.
The version of the updated document.
YES
1
List of HTTP ElasticSearch servers.
Must be an URI like https://elasticsearch.com: 9200
with scheme and port.
NO
Basic auth configuration.
YES
List of HTTP headers to be send on every request.
Must be a string with key value separated with :
, ex: Authorization: Token XYZ
.
YES
Sets the path's prefix for every request used by the HTTP client.
For example, if this is set to /my/path
, then any client request will become /my/path/
+ endpoint.
In essence, every request's endpoint is prefixed by this pathPrefix
.
The path prefix is useful for when ElasticSearch is behind a proxy that provides a base path or a proxy that requires all paths to start with '/'; it is not intended for other purposes and it should not be supplied in other scenarios.
YES
Whether the REST client should return any response containing at least one warning header as a failure.
YES
Trust all SSL CA certificates.
Use this if the server is using a self signed SSL certificate.
YES
Basic auth password.
YES
Basic auth username.