I see. From looking at the documentation for "refresh" it looks like the default interval is 1 second? so yes, that would explain my scenario. I wasn't aware of the "refresh".
do you know if the interval can be decreased to less than a second? I understand there is impact to the performance of indexing if this value is lowered. Is there also impact to searching with respect to this interval?
thanks!
Ed
On Apr 13, 2014, at 1:47 AM, David Pilato wrote:
It won't be searchable until the next refresh.
GET is real time.
SEARCH is near real time.That could explain here.
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocsLe 13 avr. 2014 à 05:09, echin1999 echin1999@gmail.com a écrit :
Hi.
I'm adding to my elasticSearch database (v. 0.90) an object via this java call.
IndexResponse response = _client.prepareIndex(SomeIndex, SomeType, SomeId).setSource(SomeJSON).execute().actionGet();
If I do a search for this object immediately after, i notice i sometimes don't find it. I assume this is because it is an asynchronous call. Is that correct?
The documentation mentions the following:
The index API allows to set the threading model the operation will be performed when the actual execution of the API is performed on the same node (the API is executed on a shard that is allocated on the same server).
The options are to execute the operation on a different thread, or to execute it on the calling thread (note that the API is still async). By default, operationThreaded is set totrue which means the operation is executed on a different thread.
Will setting operationThreaded to false guarantee that the object be available for search immediately after? The snippet above mentions "(note that the API is still async)" - so I'm guessing no. Is there a way to make the api call synchronous so i can be assured that on my next search for the object, it will definitely be there?
thanks
Ed--
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/766927ea-6943-44f5-8da2-997d1ff1b2f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.--
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/DWN30UYzeN4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CFA2AD64-8C61-44E7-A63A-79B02B257EE5%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.
--
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/1A41EBDC-7539-4BAC-8C69-2B17B33ADCD0%40gmail.com.
For more options, visit https://groups.google.com/d/optout.