Jason, Have you thought of using transactional tasks to update the search index? Or are you more concerned with concurrent updates to the same model?
- Bryce On Wednesday, April 17, 2013 3:08:05 PM UTC-7, Jason Collins wrote: > > We've been doing a fair amount of work with Search API lately. Some of the > current challenges seem to be around operations aspects. E.g., we're trying > to keep the search documents in sync with datastore entities. Because > transactions don't extend across datastore and search indexes, they can get > out of sync. So we occasionally need to look for orphaned search documents > which means walking across them all and looking to datastore to see if the > entity exists. > > This is very challenging given current quotas and something like the > MapReduce library would be very, very helpful (specifically key-splitting / > sharding) so that we could perform this operation in a smaller amount of > time. > > j > > On Wednesday, 17 April 2013 13:59:10 UTC-6, Kaan Soral wrote: >> >> I haven't even considered reading the Search API documents up until >> yesterday, the production limitations of the Search API made me consider it >> as a non-existent feature. >> >> However it seems a lot of time has passed since it was first introduced >> and after reading the documents, I really really want to use it. >> >> Is there any ETA for scalable production usage? >> Will it ever reach a point that "Total Index Size"/"API Calls" will be >> able to reach TB's/Millions? >> >> Looking forward to hearing experiences/knowledge around Search Feature. >> > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
