Thanks Mahendra.
How do you implement your batched updates? Do you fire up a cron job
every x minutes to get the "popularity" values from a database and
then use it to update Elasticsearch?
On Jun 7, 12:42 am, Mahendra M mahendr...@gmail.com wrote:
Hi Andy,
On Tue, Jun 7, 2011 at 8:42 AM, Andy selforgani...@gmail.com wrote:
I have an integer field "popularity" that is frequently updated. The
"popularity" of a document can either be increased or decreased. I use
the value of that field to help rank my search results.Even I have the same use case. A "popularity" field being updated
based on usage of a document.A search engine might not be designed for frequently updated fields
like that. Any tips on how best to handle that in Elasticsearch?How frequent are your updates ? Elasticsearch, I think, can handle
frequent updates pretty well.
Do have a look at this link -http://engineering.socialcast.com/2011/05/realtime-search-solr-vs-ela...Even so, we use some other tricks to reduce the frequency of updates.
Instead of updating Elasticsearch frequently, we collect the usage of
a document over a period of time (say 10 minutes) aggregate the result
and then update it to Elasticsearch. Maybe you can look at a similar
approach.Regards,
Mahendra