# Elasticsearch 2.1.2 after update , unexpected result

**URL:** <https://discuss.elastic.co/t/elasticsearch-2-1-2-after-update-unexpected-result/178853>\
**Category:** Elasticsearch\
**Created:** [April 29, 2019, 7:34am UTC](https://discuss.elastic.co/t/elasticsearch-2-1-2-after-update-unexpected-result/178853 "2019-04-29T07:34:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 29, 2019, 9:19am UTC](https://discuss.elastic.co/t/elasticsearch-2-1-2-after-update-unexpected-result/178853/4 "2019-04-29T09:19:52Z")

</div>

Some comments:

- Use `_doc` instead of `cross_dms_receive_send_diff` type name. Type are going to be removed in the future.
- Depending on the `waybill_code` mapping, your `term` query with `VD52794532626` may not match.
- in the future please provide a full recreation script as described in [About the Elasticsearch category](https://discuss.elastic.co/t/about-the-elasticsearch-category/21). It will help to better understand what you are doing. Please, try to keep the example as simple as possible.

A full reproduction script will help readers to understand, reproduce and if needed fix your problem. It will also most likely help to get a faster answer.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-2-1-2-after-update-unexpected-result/178853)._