Hi Venkatesh, I'm not familiar with the SearchableModel. I don't do Python. But I did a quick search and read a blog on it. It does indeed look like the __searchable_text_index property is a multi-valued property that gets added for you and it looks like it has been updated to instead move this information to a separate entity because of an exploding indexes problem. If you haven't already seen this please take a look. http://www.billkatz.com/2009/6/Simple-Full-Text-Search-for-App-Engine
It's my belief that all the extra storage is based on this exploding index. If you haven't already done so I'd update to the new SearchableModel method and/or come up a different method. To verify that the index is the problem, I'd drop the current index that was created and after a day or so see if the usage drops. It takes a day or more for index usage to be reflected in total usage from what I've seen so far (maybe sooner depending on when your statistics get run). Hope this helps, Stephen On Jul 29, 10:36 pm, Venkatesh Rangarajan <[email protected]> wrote: > Here is the exact query > > results = models.Jobs.all().search(keyword.lower()) > > Rgds > Venakatesh -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
