# Cross\_fields and boost - Is it feasible?

**URL:** <https://discuss.elastic.co/t/cross-fields-and-boost-is-it-feasible/134219>\
**Category:** Elasticsearch\
**Created:** [June 1, 2018, 12:14pm UTC](https://discuss.elastic.co/t/cross-fields-and-boost-is-it-feasible/134219 "2018-06-01T12:14:53Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![lapilit](https://avatars.discourse-cdn.com/v4/letter/l/7ba0ec/32.png) [@lapilit](https://discuss.elastic.co/u/lapilit)\
**Post date:** [June 5, 2018, 11:58am UTC](https://discuss.elastic.co/t/cross-fields-and-boost-is-it-feasible/134219/11 "2018-06-05T11:58:27Z")

</div>

@Mark_Harwood Thanks for detailed explanation. It confirms what I already understood.

> [@Mark\_Harwood](#):
>
> All the subtlety of this per-word score-tweaking is undone if you just slap a global boost on a field.

**As I see, it's actually not undone, right?** E.g. if user-boost is provided for "first name", it evens out IDF-scores for every query-term and only then applies the boost for "first name" field (for every query-term). At the same time, user-boost is not provided for "last name", so it evens out IDF-scores for "last name" field and the boost "1" remains by default.

Also, I still don't get why can't we use `cross_fields` on big-free-text fields.

---

_[View the full topic](https://discuss.elastic.co/t/cross-fields-and-boost-is-it-feasible/134219)._
