# Elasticsearch filter plugin not working

**URL:** <https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532>\
**Category:** Logstash\
**Created:** [December 4, 2019, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532 "2019-12-04T12:30:11Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![namali](https://avatars.discourse-cdn.com/v4/letter/n/a87d85/32.png) [@namali](https://discuss.elastic.co/u/namali)\
**Post date:** [December 4, 2019, 12:30pm UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532/1 "2019-12-04T12:30:11Z")

</div>

running multiple configs in logstash server. Last config, querying the previous logs in elasticsearch which have transferred by other config files in logstash server.

filter{  
...  
elasticsearch {  
hosts =\> ["XXXXXX/"]  
index =\> "act\_test"  
query =\> "tourid:%{[data][id]}"  
fields =\> { "vendorcitycode" =\> "vendorcitycode\_"  
"location" =\> "location\_"  
"imagethumbnailurl" =\> "imagethumbnailurl\_" }

...  
}

log says no mapping found , but tourid 266152 already there in act\_test in ELK

[2019-12-04T10:14:25,698][WARN][logstash.filters.elasticsearch] Failed to query elasticsearch for previous event {:index=\>"act\_test", :query=\>"tourid:266152", :event=\>#LogStash::Event:0x6625ba12, :error=\>"#\<Elasticsearch::Transport::Transport::Errors::BadRequest: [400] {"error":{"root\_cause":[{"type":"query\_shard\_exception","reason":"No mapping found for [@timestamp] in order to sort on","index\_uuid":"5TY-QtlrQWiwUkGj63unOw","index":"act\_test"}],"type":"search\_phase\_execution\_exception","reason":"all shards failed","phase":"query","grouped":true,"failed\_shards":[{"shard":0,"index":"act\_test","node":"vrtCsitlT-GGkmSrRaO9Hg","reason":{"type":"query\_shard\_exception","reason":"No mapping found for [@timestamp] in order to sort on","index\_uuid":"5TY-QtlrQWiwUkGj63unOw","index":"act\_test"}}]},"status":400}\>"}

Seems last config read before commit the previous logs in ELK. all config files run in given priority order

---

<div class="post-metadata">

**Author:** ![Julien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julien/32/19688_2.png) [@Julien](https://discuss.elastic.co/u/Julien)\
**Post date:** [December 5, 2019, 7:47pm UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532/2 "2019-12-05T19:47:31Z")

</div>

The plugin uses @timestamp by default for [sorting](https://www.elastic.co/guide/en/logstash/current/plugins-filters-elasticsearch.html#plugins-filters-elasticsearch-sort), can you check if act\_test has a field called "@timestamp" ?

---

<div class="post-metadata">

**Author:** ![namali](https://avatars.discourse-cdn.com/v4/letter/n/a87d85/32.png) [@namali](https://discuss.elastic.co/u/namali)\
**Post date:** [December 6, 2019, 9:38am UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532/3 "2019-12-06T09:38:35Z")

</div>

Hi Julien,  
Thx for the reply. @timestamp" ? there in act\_test. problem is data pushing to act\_test config also there. seems last conf file trying to read before commit act\_test.

---

<div class="post-metadata">

**Author:** ![Julien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julien/32/19688_2.png) [@Julien](https://discuss.elastic.co/u/Julien)\
**Post date:** [December 9, 2019, 10:36pm UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532/4 "2019-12-09T22:36:43Z")

</div>

Maybe [pipeline to pipeline](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html) feature may help you if you need a specific order of execution, if all conf file are part of the same pipeline there is not really an order you can rely on  
Thanks  
Julien

---

<div class="post-metadata">

**Author:** ![namali](https://avatars.discourse-cdn.com/v4/letter/n/a87d85/32.png) [@namali](https://discuss.elastic.co/u/namali)\
**Post date:** [December 10, 2019, 3:19am UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532/5 "2019-12-10T03:19:16Z")

</div>

Hi, all config execute in order. I have name all config files in alphabetical order according to priority.

---

<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:** [January 7, 2020, 3:19am UTC](https://discuss.elastic.co/t/elasticsearch-filter-plugin-not-working/210532/6 "2020-01-07T03:19:29Z")

</div>

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