# ES doesn't take into account field level boost in prefix query over catch-all field?

**URL:** <https://discuss.elastic.co/t/es-doesnt-take-into-account-field-level-boost-in-prefix-query-over-catch-all-field/15987>\
**Category:** Elasticsearch\
**Created:** [February 24, 2014, 11:57am UTC](https://discuss.elastic.co/t/es-doesnt-take-into-account-field-level-boost-in-prefix-query-over-catch-all-field/15987 "2014-02-24T11:57:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene\_I](https://avatars.discourse-cdn.com/v4/letter/e/ce7236/32.png) [@Eugene\_I](https://discuss.elastic.co/u/Eugene_I)\
**Post date:** [February 24, 2014, 11:57am UTC](https://discuss.elastic.co/t/es-doesnt-take-into-account-field-level-boost-in-prefix-query-over-catch-all-field/15987/1 "2014-02-24T11:57:41Z")

</div>

Greetings everyone,

I've faced with a following issue, and I'm not sure whether it's ES  
peculiarity or something is wrong with my setup.

1. Created ES mapping with two string fields, one of them is with  
customized boost.
2. Performed term search over default catch-all field and observed expected  
result -- sample doc containing the search term in the field with  
customized boost has a higher score.
3. Performed prefix query with customized rewrite over default catch-all  
field and got response which confuses me. ES ignores the field level boost  
in this case.

So, the question is - is it possible to get for prefix query the response  
which honors field level boost factor, as term query does?

The setup: [https://gist.github.com/ei82/776d42d6a59262529c54](https://gist.github.com/ei82/776d42d6a59262529c54)

Thanks,  
Eugene,

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8ac1f92a-857c-43e2-8f11-64bbedd6d357%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ac1f92a-857c-43e2-8f11-64bbedd6d357%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Maxim\_Vorobyov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maxim_vorobyov/32/1775_2.png) [@Maxim\_Vorobyov](https://discuss.elastic.co/u/Maxim_Vorobyov)\
**Post date:** [February 25, 2014, 11:36am UTC](https://discuss.elastic.co/t/es-doesnt-take-into-account-field-level-boost-in-prefix-query-over-catch-all-field/15987/2 "2014-02-25T11:36:48Z")

</div>

Hi All. I have the same issue and would highly appreciate answer.  
Many Thanks! Maxim

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/31a85891-ab76-402a-83a0-bbf442defc00%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/31a85891-ab76-402a-83a0-bbf442defc00%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 1:47am UTC](https://discuss.elastic.co/t/es-doesnt-take-into-account-field-level-boost-in-prefix-query-over-catch-all-field/15987/3 "2017-07-06T01:47:29Z")

</div>


