# Elasticsearch clickthrough relevance ranking

**URL:** <https://discuss.elastic.co/t/elasticsearch-clickthrough-relevance-ranking/13600>\
**Category:** Elasticsearch\
**Created:** [September 13, 2013, 7:48pm UTC](https://discuss.elastic.co/t/elasticsearch-clickthrough-relevance-ranking/13600 "2013-09-13T19:48:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rafael\_Almeida](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rafael_almeida/32/1345_2.png) [@Rafael\_Almeida](https://discuss.elastic.co/u/Rafael_Almeida)\
**Post date:** [September 13, 2013, 7:48pm UTC](https://discuss.elastic.co/t/elasticsearch-clickthrough-relevance-ranking/13600/1 "2013-09-13T19:48:24Z")

</div>

Hello,

I have been reading about lucidworks search. One interesting feature I  
found on it was what they call "click tracking and boosting". I haven't  
find anything like it in elastic search world (hopefully because of lack of  
google querying skills). The feature works like this: the user makes a  
query and clicks on a result. That click is tracked and it boosts the score  
of that document for the query.

Reading more about lucid's implementation, it seems like they create a  
"clicks" index along with the main index. The click index has a clicks\_term  
field which holds queries for that particular document. Each query has a  
weight proportional to the number of times the document was clicked on that  
given query. They make it like that so they can reindex the documents  
faster than a full reindex of all the fields for each document. Both  
indices are read using ParallelReader in order to merge the fields (that  
was pre-4.0, now ParallelReader seems to have two flavours: Atomic and  
Composite. I don't know the difference). I'm not completely sure on any of  
this, but that's what I have understood so far.

Anyway, is there any work on doing that sort of thing with elastic search?  
How easy would it be to use ParallelReader on ES? Would it make sense?

[]'s  
Rafael

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Srinivasan\_Ramaswamy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/srinivasan_ramaswamy/32/74106_2.png) [@Srinivasan\_Ramaswamy](https://discuss.elastic.co/u/Srinivasan_Ramaswamy)\
**Post date:** [June 1, 2016, 10:54pm UTC](https://discuss.elastic.co/t/elasticsearch-clickthrough-relevance-ranking/13600/2 "2016-06-01T22:54:59Z")

</div>

I am wondering about the same question now. I am curious to learn how you solved your problem.

---

<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 5, 2017, 10:47pm UTC](https://discuss.elastic.co/t/elasticsearch-clickthrough-relevance-ranking/13600/3 "2017-07-05T22:47:06Z")

</div>