I too worry about this limit, and am hoping that the limit at least applies per-index, and not per-application. We are using Search API in production today and our per-application usage is growing fast.
re: re-sync: working in bulk against the search API is challenging today. There is a per-minute (or -second) rate limit such that if you use M-R to do something against Search API, you can toast your rate limit and affect end-users. To counter-act, we pipe our batch processes through a rate-limited queue so that we only use a portion (half) of the allowed rate limit. This preserves the end-user functionality, but of course, it takes _forever_ to get these batch processes through the queue... j On Wednesday, 4 September 2013 16:42:42 UTC-6, Kaan Soral wrote: > > This is really bothering me, the issue is always deep in my mind, the > reason I use appengine is the possibility of near-infinite scalability, > however the search index size limitation will prevent any decent use-case > of this beyond-awesome feature > > It would be devastating to reach the 250gb limit with an app that is > utilizing Search API for actual search functionality, at that point, the > situation will probably be worse than not having search functionality at > all, even if the limit gets increased after that, it would be challenging > to re-sync data, if needed > > Is there anyone using Search API on production, does the limits get > increased? If so I wonder how much, is it *theoretically* possible to > reach 100TB's of something like that? > > Thanks in Advance > -- 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.
