Reputation: 4255
In all the elasticsearch examples I've seen so far, every index request that needs to use an ingest pipeline passes it as query parameter like
PUT /<target>/_doc/<_id>?pipeline=my_pipeline
Is this the only way to use the pipeline when indexing documents? Or are there also other ways to utilize the pipelines?
Upvotes: 2
Views: 7596
Reputation: 297
Elastic Filebeat documentation recommends configuring the pipeline as early as possible, in the input. From any filebeat input method common documentation:
The pipeline ID can also be configured in the Elasticsearch output, but this option usually results in simpler configuration files. If the pipeline is configured both in the input and output, the option from the input is used.
Upvotes: 0
Reputation: 217564
That's only one of the options, there are plenty of ways to leverage ingest pipelines. You can also:
You can also define a default pipeline to be used when indexing documents inside an index with the index.default_pipeline
setting and the index.final_pipeline
setting, so as not to have to specify it in each indexing request (as in your question).
You can also specify it in the elasticsearch
Logstash output plugin or in the Filebeat elasticsearch
output](https://www.elastic.co/guide/en/beats/filebeat/current/elasticsearch-output.html#pipeline-option-es).
Upvotes: 9