I have a related question about synchronous behavior of Java APIs. I understand refresh will make sure that the indexed document becomes searchable but what about subsequent updates / deletes to the same document.
If I index a document and it is going to be done asynchronously does that mean an immediate update or delete on this document could potentially fail because the document is not yet actually saved? Note that the update/ delete could be coming from potentially different client but still serially. Is there a API like "flush" which guarantees that everything that has been indexed so far is now available in ES (not for search but for get/update/delete) at least in the trans log. On Sunday, April 13, 2014 8:34:19 AM UTC-7, Jörg Prante wrote: > > There is massive impact - but try and see for yourself. > > Jörg > > > On Sun, Apr 13, 2014 at 4:54 PM, Edward Chin <echi...@gmail.com > <javascript:>> wrote: > >> If I do that, and there are concurrent threads doing the same thing, is >> there impact to threads that are simply searching? I don't mind the >> indexing threads being slow, but i don't want to impact the search threads >> too much. >> >> thanks >> ed >> >> On Apr 13, 2014, at 10:47 AM, joerg...@gmail.com <javascript:> wrote: >> >> Look at IndexRequestBuilder, there is a method setRefresh(true) so you >> can enforce a post refresh per index request. >> >> Jörg >> >> >> >> -- >> 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 >> elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHJay-pvs%3D4QoOyfYs%3DZkC_fQTtedO%2B6EeS0iyL_KHffA%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHJay-pvs%3D4QoOyfYs%3DZkC_fQTtedO%2B6EeS0iyL_KHffA%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> >> 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 elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/5F90E219-EAF2-41AA-848D-99D27CB0952F%40gmail.com >> >> <https://groups.google.com/d/msgid/elasticsearch/5F90E219-EAF2-41AA-848D-99D27CB0952F%40gmail.com?utm_medium=email&utm_source=footer> >> . >> >> 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/f143fb0f-625f-4965-8416-346017080b0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
