I know there have been a lot of posts about the refresh api and trying to
achieve real time searching. We have a situation where we update a bunch
documents and then we call refresh in an attempt to make them immediately
available to the search API (not the get API), but we have found that, that
is not the case. Does the refresh API call block until it is done
refreshing? We normally let ElasticSearch run refresh on its own, but there
are a few instances where we need changes immediately. Any suggestion?
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/12ab9e32-7345-4022-adbc-a1bd10d122a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
After banging our heads we realized it was our problem and not ES.
On Thursday, February 5, 2015 at 3:51:44 PM UTC-7, Chris Robison wrote:
I know there have been a lot of posts about the refresh api and trying to
achieve real time searching. We have a situation where we update a bunch
documents and then we call refresh in an attempt to make them immediately
available to the search API (not the get API), but we have found that, that
is not the case. Does the refresh API call block until it is done
refreshing? We normally let Elasticsearch run refresh on its own, but there
are a few instances where we need changes immediately. Any suggestion?
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fe262a59-1a33-43a1-95d8-58284fe5beba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.