Yes, I have read them and had even tried the vacuum_indexes procedure. It did not work, as I had mentioned in my mail.
Tried it again today and they got deleted at once from my indexes. By the way, the problem is not related to exploding indexes - there were 3 new indexes of 2 to 3 properties each, all properties were string/integer properties and the data to be indexed was less than 100. I just discovered that it *might* be because one of the index definition had a non-existing property name specified. I am not going to try it again with a wrong property name in the index, to confirm the reason for the "Error" :-). But, just in case any of you face a similar problem, see if this might be the reason. Regards, R.Rajkumar On Mon, May 18, 2009 at 2:20 AM, ryan <[email protected]<ryanb%[email protected]> > wrote: > > have you read: > > http://code.google.com/appengine/kb/general.html#error_indexes > > http://code.google.com/appengine/docs/python/datastore/queriesandindexes.html#Big_Entities_and_Exploding_Indexes > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
