I would like to apply recency to a simple match query.
I was heading in the direction of using _timestamp in a script such as
this: "script": "_score + log(doc['_timestamp'].value)/100"
However, after reading this post regarding 90.4 function_score_query I am
confused. The document mentions recency and then goes on to use a geo
distance example. Does an example of applying recency exist?
In my use case recent docs would have some minor influence and docs older
than say a year would have 0.
I would like to apply recency to a simple match query.
I was heading in the direction of using _timestamp in a script such as
this: "script": "_score + log(doc['_timestamp'].value)/100"
However, after reading this post regarding 90.4 function_score_query I am
confused. The document mentions recency and then goes on to use a geo
distance example. Does an example of applying recency exist?
In my use case recent docs would have some minor influence and docs older
than say a year would have 0.
On Tue, Nov 26, 2013 at 9:53 PM, Kevin S <kevin...@gmail.com <javascript:>
wrote:
I would like to apply recency to a simple match query.
I was heading in the direction of using _timestamp in a script such as
this: "script": "_score + log(doc['_timestamp'].value)/100"
However, after reading this post regarding 90.4 function_score_query I am
confused. The document mentions recency and then goes on to use a geo
distance example. Does an example of applying recency exist?
In my use case recent docs would have some minor influence and docs older
than say a year would have 0.
if you need arbitrarily complex functions, I think the script score as
you described is most useful. But you have to compute distance and
decay yourself in the script.
The decay functions are separate from the script scoring and can only
be combined with other functions as described in the documentation
(sum, avg,...). The only weighting can be achieved in a sum by using a
"bool" query with "disable_coord": true.
I hope that helps.
That is the page I intended to link to in my original post.
It is still not clear how to use _timestamp in the calculations.
What I would love to see in an example that would contrast: Heavy weight on
_score, light on recency. vs Heavy on recency, light on _score.
This functionality was very easy to do on the platform I am moving from
where an "age" variable was available allowing calculations such as: (-age +
relevance^2) or (-age^2 + relevance). I'm trying to duplicate that.
Thanks.
On Wednesday, November 27, 2013 3:03:30 AM UTC-8, Adrien Grand wrote:
Hi Kevin,
There are examples on the function_score documentation page about dates
and prices that should help:
I would like to apply recency to a simple match query.
I was heading in the direction of using _timestamp in a script such as
this: "script": "_score + log(doc['_timestamp'].value)/100"
However, after reading this post regarding 90.4 function_score_query I am
confused. The document mentions recency and then goes on to use a geo
distance example. Does an example of applying recency exist?
In my use case recent docs would have some minor influence and docs older
than say a year would have 0.
Thank you.
--
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 elasticsearc...@googlegroups.com.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.