description<\/code> Description or purpose of the pipeline<\/li>\nprocessors<\/code> List of processors. Each processor transforms the document in some specific way.\u00a0<\/li>\n<\/ol>\n\n- You might hear or ingest node, bulk api these concepts are not similar but do overlap.<\/li>\n
- To use a pipeline, simply specify the pipeline parameter on an index or bulk request.\u00a0<\/li>\n<\/ul>\n
Ingest Node<\/h2>\n
Ingest node pre-process’s documents before the actual document indexing happens. The ingest node intercepts bulk and index requests, it applies transformations, and it then passes the documents back to the index or bulk APIs.<\/p>\n
\nAll nodes in a cluster enable ingest by default<\/code>, so any node can handle ingest tasks.\u00a0<\/p>\n<\/blockquote>\nTo pre-process documents before indexing PIPELINES<\/code> are used.<\/p>\nSome key considerations<\/p>\n
\n- An index<\/a> may also declare a\u00a0default pipeline\u00a0that will be used in the absence of the\u00a0pipeline\u00a0parameter.<\/li>\n
- Index may also declare a final pipeline<\/a> that will be executed after any request or default pipeline (if any).<\/li>\n<\/ul>\n
How can we use it?<\/h3>\n
It is as simple as specifying a parameter in the URL<\/p>\n
\nPUT my-index\/_doc\/my-id?pipeline=my_pipeline_id<\/code>
{
\u00a0 \u00a0 \u00a0 \u00a0 “foo”: “bar”
}<\/p>\n<\/blockquote>\nIngest API’s<\/h2>\n
There are specifically 4 kinds of _ingest API’s<\/p>\n
\n- PUT pipeline<\/li>\n
- GET pipeline<\/li>\n
- Delete pipeline<\/li>\n
- Simulate pipeline<\/li>\n<\/ol>\n
PUT Pipeline<\/h2>\n
Allows to put create, or update a pipeline<\/p>\n
\nPUT _ingest\/pipeline\/fix_my_locales {<\/p>\n
“description”: ” My first pipeline”,<\/p>\n
“processors”: []<\/p>\n
}<\/p>\n<\/blockquote>\n
Official documentation here<\/a>.<\/p>\nfix_my_locales<\/code> is the pipeline id that you wish to provide.<\/p>\n
![\"\"](\"https:\/\/blog.samarthya.me\/wps\/wp-content\/uploads\/2020\/04\/Screenshot-2020-04-23-at-3.15.47-PM.png\")
<\/p>\n