Index time boosting Vs Query time boosting

Elastic Stack Elasticsearch
1

Hi

Which scenarios would support index time boosting over query time
boosting and vice-versa. How does one score over an other and what to keep
in mind while making a decision about one approach?

Karan

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

2

I would personally say use query time boosting all the time. Using index
time boosting you need to reindex to change the boosting behaviour.
What is your usecase?

On Tuesday, October 15, 2013 3:19:17 AM UTC+2, Karan Verma wrote:

Hi

Which scenarios would support index time boosting over query time
boosting and vice-versa. How does one score over an other and what to keep
in mind while making a decision about one approach?

Karan

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

3

Thanks for your answer Luca. I am doing a full text search on a name of the
person, city, state, and specialty. Query time boosting sounds convenient
but I wanted to understand why we have index time boosting and is it faster
or higher performance to use it.

Also would be an overkill if I boost results booth during Index time and
query time. Are there any usecases for doing both?

On Tue, Oct 15, 2013 at 9:44 AM, Luca Cavanna cavannaluca@gmail.com wrote:

I would personally say use query time boosting all the time. Using index
time boosting you need to reindex to change the boosting behaviour.
What is your usecase?

On Tuesday, October 15, 2013 3:19:17 AM UTC+2, Karan Verma wrote:

Hi

Which scenarios would support index time boosting over query time
boosting and vice-versa. How does one score over an other and what to keep
in mind while making a decision about one approach?

Karan

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/n0n65sNKJEc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Best,
Karan

Life saving Ninja & Software Engineer

Karan pronounced Ka (http://tiny.cc/0lu61w) + Run

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

4

It is not overkill, and there are of course use cases.

The boost factor at index time sets a document related boost. That is, a
factor depending on the nature of the document is being set in the
relevance scoring formula. Example: the number of links pointing to this
document (also known as popularity or authority ranking in web search).
Such a boost factor is also called "static boost" since it does not change
from query to query. If static boost must change, the whole document must
be reindexed.

The boost factor given at query time is query term related. That is, a
factor depending on a term in the query is being set in the relevance
scoring formula. Example: hits on docs with a certain term should be ranked
higher than hits on docs with other terms in the query. Such a boost factor
is called "dynamic boost" because it can change from query to query. There
is no need to reindex docs.

There is no difference in performance since the standard scoring algorithm
always takes both static and dynamic boost factors into account.

Jörg

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

5

I see. Thanks Jörg.

On Tue, Oct 15, 2013 at 5:36 PM, joergprante@gmail.com <
joergprante@gmail.com> wrote:

It is not overkill, and there are of course use cases.

The boost factor at index time sets a document related boost. That is, a
factor depending on the nature of the document is being set in the
relevance scoring formula. Example: the number of links pointing to this
document (also known as popularity or authority ranking in web search).
Such a boost factor is also called "static boost" since it does not change
from query to query. If static boost must change, the whole document must
be reindexed.

The boost factor given at query time is query term related. That is, a
factor depending on a term in the query is being set in the relevance
scoring formula. Example: hits on docs with a certain term should be ranked
higher than hits on docs with other terms in the query. Such a boost factor
is called "dynamic boost" because it can change from query to query. There
is no need to reindex docs.

There is no difference in performance since the standard scoring algorithm
always takes both static and dynamic boost factors into account.

Jörg

--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/n0n65sNKJEc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Best,
Karan

Life saving Ninja & Software Engineer

Karan pronounced Ka (http://tiny.cc/0lu61w) + Run

--
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.
For more options, visit https://groups.google.com/groups/opt_out.