It's probably a much better idea to handle it in a pre-put hook and not always update the search document and mark it as updated when you do
Search seems to be very limited in terms of quotas (seems very limited, in reality it might be the opposite, I don't even see an index cap from the quota UI, yet it should be 1GB's or something) There was also a hidden schema system a while ago, so watch out for that one, I guess it's improved now, but you could bust the schema and break the search feature for a single index, some while ago (so make sure you don't use many properties for the search document) ----- I've been using and loving the search feature for a while now, without any issues I have nearly a million entities indexed, the lack of quota/size information is a bit concerning :) -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
