On Mon, Jan 20, 2014 at 2:57 AM, Ananthakrishnan Venkatasubramanian < ananthakrishnan.venkatasubraman...@a-cti.com> wrote:
> Clearly the search request came into the instance that has been running > for some time. Document was indexed successfully at 12:00:09 (UTC) and the > request for search came in at 12:00:45 (UTC), 12:01:47 (UTC), 12:01:49 > (UTC), 12:03:08 (UTC) & 12:03:24 (UTC). > > Only in the last request came in at 12:03:24 (UTC), the results came > successfully (1 record found) and the other 4 requests for search which > came after indexing the document failed to return results (ie...0 records > found was the result being returned). > So to clarify, your issue is that the Search API didn't return the document until 3 minutes 15 seconds after the initial "index successful" operation? Did you try any requests after the 12:03:24 UTC mark? That sounds about correct actually. It's not a bug, it's just that the Search API requires a little time between the *index.put* operation to the time where the document is available for search. The fact that *index.put* returned successfully doesn't mean that the document is fully indexed, it means that the App Engine infrastructure acknowledges your request but will need some time to replicate the document, replicate the indexes, push the updates over the network, receive acknowledgements, etc. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
