# Failed to execute pipeline for a bulk request after a successfull ingest plugin

**URL:** <https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-after-a-successfull-ingest-plugin/98354>\
**Category:** Elasticsearch\
**Created:** [August 25, 2017, 9:37am UTC](https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-after-a-successfull-ingest-plugin/98354 "2017-08-25T09:37:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin.d](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@martin.d](https://discuss.elastic.co/u/martin.d)\
**Post date:** [August 25, 2017, 9:37am UTC](https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-after-a-successfull-ingest-plugin/98354/1 "2017-08-25T09:37:53Z")

</div>

Hi, I made an ingest plugin for Eleasticsearch 5.4.0, the ingest plugin works well in simulate mode .  
but in standard mode I have a "failed to execute pipeline for a bulk request" message in the logs after the execution of the processor.

so:

- if I use the pipeline in simulate mode =\> the processor works.
- if I don't use the pipeline ( in logstash or Dev console ) =\> the document is inserted.
- if I use the pipeline ( in logstash or Dev console ) =\> the processor is executed but the document is not inserted. and I have the following message in the logs.

Have you any Idea what I am missing ?

> ```
> [2017-08-24T18:49:23,947][ERROR][o.e.a.b.TransportBulkAction] [node_one] failed to execute pipeline for a bulk request
> java.lang.NullPointerException: null
> at org.elasticsearch.cluster.metadata.IndexNameExpressionResolver$DateMathExpressionResolver.resolveExpression(IndexNameExpressionResolver.java:775) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.cluster.metadata.IndexNameExpressionResolver.hasIndexOrAlias(IndexNameExpressionResolver.java:251) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.support.AutoCreateIndex.shouldAutoCreate(AutoCreateIndex.java:73) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.bulk.TransportBulkAction.shouldAutoCreate(TransportBulkAction.java:214) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.bulk.TransportBulkAction.doExecute(TransportBulkAction.java:160) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.bulk.TransportBulkAction.lambda$processBulkIndexIngestRequest$3(TransportBulkAction.java:526) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.ingest.PipelineExecutionService$2.doRun(PipelineExecutionService.java:98) [elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638) [elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.4.0.jar:5.4.0]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> [2017-08-24T18:49:23,948][WARN][r.suppressed] path: /lookup/Patient/1, params: {pipeline=lookup, index=lookup, id=1, type=Patient}
> java.lang.NullPointerException: null
> at org.elasticsearch.cluster.metadata.IndexNameExpressionResolver$DateMathExpressionResolver.resolveExpression(IndexNameExpressionResolver.java:775) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.cluster.metadata.IndexNameExpressionResolver.hasIndexOrAlias(IndexNameExpressionResolver.java:251) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.support.AutoCreateIndex.shouldAutoCreate(AutoCreateIndex.java:73) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.bulk.TransportBulkAction.shouldAutoCreate(TransportBulkAction.java:214) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.bulk.TransportBulkAction.doExecute(TransportBulkAction.java:160) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.action.bulk.TransportBulkAction.lambda$processBulkIndexIngestRequest$3(TransportBulkAction.java:526) ~[elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.ingest.PipelineExecutionService$2.doRun(PipelineExecutionService.java:98) [elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:638) [elasticsearch-5.4.0.jar:5.4.0]
> at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) [elasticsearch-5.4.0.jar:5.4.0]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> 
> ```

---

<div class="post-metadata">

**Author:** ![martin.d](https://avatars.discourse-cdn.com/v4/letter/m/839c29/32.png) [@martin.d](https://discuss.elastic.co/u/martin.d)\
**Post date:** [August 25, 2017, 4:36pm UTC](https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-after-a-successfull-ingest-plugin/98354/2 "2017-08-25T16:36:35Z")

</div>

I still don't know why the "failed to execute pipeline for a bulk request" error occured but after some reorganisation of the code every thing works as expected.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 22, 2017, 4:36pm UTC](https://discuss.elastic.co/t/failed-to-execute-pipeline-for-a-bulk-request-after-a-successfull-ingest-plugin/98354/3 "2017-09-22T16:36:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
