| 123456789101112131415161718192021222324252627282930313233343536373839404142 | [[ingest]]= Ingest Node[partintro]--Use an ingest node to pre-process documents before the actual document indexing happens. The ingest node intercepts bulk and index requests, it applies transformations, and it thenpasses the documents back to the index or bulk APIs.All nodes enable ingest by default, so any node can handle ingest tasks. You can also creatededicated ingest nodes. To disable ingest for a node, configure the following setting in theelasticsearch.yml file:[source,yaml]--------------------------------------------------node.ingest: false--------------------------------------------------To pre-process documents before indexing, <<pipeline,define a pipeline>> that specifies a series of<<ingest-processors,processors>>. Each processor transforms the document in some specific way. For example, apipeline might have one processor that removes a field from the document, followed byanother processor that renames a field. The <<cluster-state,cluster state>> then storesthe configured pipelines.To use a pipeline, simply specify the `pipeline` parameter on an index or bulk request. Thisway, the ingest node knows which pipeline to use. For example:[source,js]--------------------------------------------------PUT my-index/_doc/my-id?pipeline=my_pipeline_id{  "foo": "bar"}--------------------------------------------------// CONSOLE// TEST[catch:bad_request]See <<ingest-apis,Ingest APIs>> for more information about creating, adding, and deleting pipelines.--include::ingest/ingest-node.asciidoc[]
 |